Oracle Database / RMAN Backup & Recovery
RMAN-06172: locate the intended control-file autobackup
A recovery session may not find an autobackup because its DBID, search range, device or format does not match. Confirm the source 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.
SHOW CONTROLFILE AUTOBACKUP;Read the result
In an appropriate RMAN target context, this reports the current setting. During disaster recovery without a mounted target, use documented recovery metadata instead of assuming this is available.
Resolve and verify
Compare saved DBID and autobackup naming or media information with the recovery runbook. Search the correct media and time range through the authorized procedure.
Operational precautions
Do not substitute another database's control file or guess the DBID based on a similar name.