See which backups a restore would use and validate them (PREVIEW / VALIDATE)
OracleRMANCommand
# Backups and archivelogs a restore needs (without reading the files):
RESTORE DATABASE PREVIEW SUMMARY;
# For a return to a point in time:
RESTORE DATABASE UNTIL TIME "TO_DATE('2026-01-15 03:00:00','YYYY-MM-DD HH24:MI:SS')" PREVIEW;
# Validate the backups by actually reading them (without restoring):
RESTORE DATABASE VALIDATE;
RESTORE ARCHIVELOG FROM TIME 'SYSDATE-1' VALIDATE;
RESTORE CONTROLFILE VALIDATE;
RESTORE SPFILE VALIDATE;What it does
PREVIEW reports from the catalog/controlfile which backup sets/copies and which archivelog range a restore would use; VALIDATE actually reads those backups and verifies there is no corruption or missing file.
When to use it
For planning before a real restore, to prove the backup strategy meets the RPO target, and as a periodic restore test.
Caution
PREVIEW looks only at the records; it is misleading if files were deleted, so run CROSSCHECK first or use RESTORE ... VALIDATE. VALIDATE reads the whole backup; it can take long over tape/network. Make the date depend on the TO_DATE mask, not on the session NLS settings.
Related
- Create an RMAN recovery catalog and register the database
- Create a physical standby from the active database with RMAN DUPLICATE
- Validate and clean up RMAN backup records (CROSSCHECK, EXPIRED, OBSOLETE)
- Validate the database and backups against corruption (VALIDATE)
- Repair corrupt blocks online (block media recovery, RECOVER CORRUPTION LIST)
- Return a tablespace to a point in the past (TSPITR)