RelationalDBDesign RelationalDBDesign


Incomplete Recovery   «Prev 

Performing Recovery through RESETLOGS

When you perform recovery through RESETLOGS, make sure you follow the steps in the order that they are presented. Do not skip any of the steps in the process.
  1. Make a backup of the current database control file.
  2. Restore the datafiles and control files from the backup taken before you opened the current database with the RESETLOGS option.
  3. Start the database in mount mode.
  4. In your alert logs, find the change number at the completion of your last incomplete recovery.
  5. Recover the database via the RECOVERY DATABASE UNTIL CHANGE <CHANGE_NUMBER> USING BACKUP CONTROLFILE; statement.
  6. Shut down the database using the NORMAL or IMMEDIATE option.
  7. Restore the current control file from the backup made in Step 1.
  8. Mount the database.
  9. Recover the database using the RECOVER DATABASE command with the appropriate option.

Oracle RMAN Backup and Recovery
If you plan to recover to the current log sequence number, you should use complete database recovery via the RECOVER [AUTOMATIC] DATABASE command. However, sometimes you may only want to recover to an earlier log sequence number and you have to use the incomplete recovery with the appropriate option and open the database with the RESETLOGS option.
  1. Open the database and check whether the data you expected to recover exists if you planned to recover to an earlier redo log sequence number. Check the data dictionary view V$LOG to ensure you recovered to the current log sequence number if you planned to recover to the current redo log sequence number.
  2. Make a whole database backup to prevent the need for this kind of recovery in the future.
To perform recovery through RESETLOGS you must have all archived logs generated after the most recent backup and at least one control file (current, backup, or created).