Oracle Database / RMAN Backup & Recovery
Check database incarnations when RMAN selects unexpected backups
An OPEN RESETLOGS creates a new recovery branch that affects backup and recovery selection. Verify the intended lineage before restoring older content.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
LIST INCARNATION OF DATABASE;Read the result
In RMAN, the list identifies known incarnations and their status. It does not determine which business recovery target is appropriate.
Resolve and verify
Compare resetlogs history, DBID and the recovery objective with the backup catalog. Have the recovery DBA select a supported path for the intended branch.
Operational precautions
Do not reset the repository's current incarnation merely to make a command accept an older backup.