Performing Time-Based or Change-Based Incomplete Recovery

This section describes how to specify an SCN or time for the end point of recovery. If your database is affected by seasonal time changes (for example, daylight savings time), then you may experience a problem if a time appears twice in the redo log and you want to recover to the second, or later time. To handle time changes, perform cancel-based or change-based recovery.

To perform change-based or time-based recovery:

1. Follows Step 1 through Step 8 in "Performing Closed Database Recovery".

2. Issue the RECOVER DATABASE UNTIL statement to begin recovery. If recovering to an SCN, then specify as a decimal number without quotation marks. For example, to recover through SCN 10034 issue:

   RECOVER DATABASE UNTIL CHANGE 10034;

   If recovering to a time, then the time is always specified using the following format, delimited by single quotation marks: ‘YYYY-MM-DD:HH24:MI:SS‘. The following statement recovers the database up to a specified time:

   RECOVER DATABASE UNTIL TIME ‘2000-12-31:12:47:30‘

3. Apply the necessary redo log files to recover the restored data files. The database automatically terminates the recovery when it reaches the correct time, and returns a message indicating whether recovery is successful.

   Note:

   Unless recovery is automated, the database supplies the name from LOG_ARCHIVE_DEST_1 and asks you to stop or proceed with after each log. If the control file is a backup, then after the archived logs are applied you must supply the names of the online logs.

4. Follow Steps 4 and 5 in "Performing Cancel-Based Incomplete Recovery".