Oracle Database / RMAN Backup & Recovery
Inventory RMAN backups before claiming a restore is possible
A successful job notification does not identify the available recovery chain. Inspect the repository and confirm which database it describes.
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 SUMMARY;Read the result
Run inside RMAN connected through the approved authentication method. Repository rows describe recorded backups; they do not prove that pieces are accessible or readable now.
Resolve and verify
Match the database identity, required recovery point and backup media. Plan an approved validation and isolated recovery test for the actual service objective.
Operational precautions
Do not expose backup paths or credentials. LIST does not retrieve missing pieces or validate their contents.