Oracle Database / RMAN Backup & Recovery
Distinguish obsolete RMAN backups from missing backup files
Retention status and physical availability answer different questions. A backup can be obsolete under policy while still present, or expired after a failed accessibility check.
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.
REPORT OBSOLETE;Read the result
The RMAN report identifies backups no longer needed under the configured retention policy. It does not delete them or prove a media copy exists.
Resolve and verify
Compare the policy with business recovery requirements and media retention. Investigate unavailable pieces separately with the storage or media manager owner.
Operational precautions
Do not run DELETE OBSOLETE or DELETE EXPIRED as a reflex response to a failed backup job.