https://support.oracle.com/epmos/faces/ ... e0rq0f9d_4
"RMAN DUPLICATE / RESTORE a database to a higher patchset (Doc ID 558408.1)"
Apparently, there are issues around restoring a database to a destination that has a higher patchset. This occasionally happens to me, as we patch non-prod first, let it run for a week or so, then we patch prod. In the interim, we occasionally receive a request to restore a copy of prod down to non-prod for testing. The most recent attempt at this failed for me after applying the October2024 Oracle CPU to my non-prod datbases, see cases #07524704 and #07514752 for details if you like.
Veeam documentation supports this too:
As noted at: https://helpcenter.veeam.com/rn/veeam_b ... notes.html
"Veeam Explorer for Oracle
...
The database restore may fail if the backed-up Oracle server version and the target server version have different patch levels.
..."
Supposedly, the issue can be resolved by issuing the following command in SQLPlus:
SQL> alter database open [resetlogs] upgrade;
If that is so, then you clever fellows can probably figure out how to automate this. I'm thinking maybe some sort of version check at the start of the process, then the appropriate commands to handle the patchset difference. I have every confidence in your abilities, good luck
