Oracle Database / RMAN Backup & Recovery
RMAN-06023: investigate why no suitable backup was found
A restore can find repository records yet lack an eligible backup for a particular datafile and recovery point. Confirm selection criteria and database identity.
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 BACKUP OF DATAFILE 1;Read the result
In RMAN, this example lists recorded backups of datafile 1. Substitute the affected file number; metadata visibility is not the same as media availability.
Resolve and verify
Check incarnation, requested time or SCN, device type and catalog completeness. Locate the correct backup through the approved repository procedure before retrying.
Operational precautions
Do not change the recovery target arbitrarily to make backup selection succeed; that changes the data recovery promise.