Oracle Database / RMAN Backup & Recovery
RMAN-06059: investigate a missing archived log without destroying evidence
A backup can fail when an archived log recorded in the repository is not accessible. Determine whether storage is temporarily missing or the file was removed.
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 ARCHIVELOG ALL;Read the result
The RMAN inventory provides expected log identities and recorded paths. It does not establish current filesystem or media accessibility.
Resolve and verify
Check the named path and recovery requirements with the storage owner. Reconcile repository status only after understanding missing content and preserving an alternate recoverable copy.
Operational precautions
Do not delete repository records or expired logs just to make the next backup show green.