First page Back Continue Last page Graphics
Simplified Recovery Through RESETLOGS (SRR)
After PIT recovery or recovery with a backup controlfile, must OPEN RESETLOGS
Now, backups taken before RESETLOGS can be used in recovery
Benefits
- No need to do full database backup after RESETLOGS
- “Old” backups can be used to recover database
- RMAN incrementals can be based on pre-RESETLOGS full backups
Transparent
- Existing RMAN RESTORE/RECOVERY scripts work
Notes:
After a point-in-time recovery (incomplete recovery) or a recovery using a backup control file, the Oracle database must be opened with the RESETLOGS operation. RESETLOGS creates a new incarnation of the database. An incarnation SCN and timestamp are recorded in the control file, data file headers, redo logs, archived logs and backup pieces.
In prior releases, backups and archive logs created before a RESETLOGS could not be used in the recovery of the current database incarnation unless an RMAN catalog was used to record all database incarnations. With Oracle10g, this is no longer true. This provides several benefits:
There is no need to do a full database backup after OPEN RESETLOGS and before opening the database for general use.
“Old” backups can be used in recovery. If newer backups are corrupted or lost, “old” backup can be used if available.
RMAN incremental backups can be based on a level 0 backup taken before RESETLOGS.
Oracle has implemented this so as to be transparent to the DBA. i.e. Existing RMAN restore and recovery scripts will work, even if they access a backup created before a RESETLOGS operation.