Recover until
The options in this drop-down list allow you to specify to which point in time you
would like the recovery to be performed.
• Now
Data Protector starts RMAN to recover the database to the most recent time
possible by applying all archived redo logs. By default, this option is selected.
• Selected time
Use this option to specify an exact time to which the archive logs are applied.
• Selected logseq/thread number
A logseq number is a redo log sequence number. Use this option to specify
a particular redo log sequence and a thread number which will act as an
upper limit of redo logs to recover.
• Selected SCN number
Use this option to specify the SCN number to which you perform the recovery.
If you reset the logs, also reset the database; otherwise, Oracle will during the
next backup try to use the logs that were already reset and the backup will fail.
Login to the target and recovery catalog database and run:
rman target Target_Database_Login catalog Recovery_Catalog_Login
RMAN> RESET DATABASE;
RMAN> exit
Open database after recovery
Opens the database after a recovery is performed.
Reset logs
Resets the archive logs after the database is opened.
Always reset the logs:
• After an incomplete recovery (not Recover until now).
• If a backup of a control file is used in recovery or restore and recovery.
Do not reset the logs:
• After a complete recovery (Recover until now) when the backup of a control
file was not used in recovery or restore and recovery.
• On the primary database, if the archive logs are used for a standby database.
However, if you must reset the archive logs, you will need to recreate the
standby database.
If you reset the logs when the Recover until option is set to Now, a warning is
displayed, stating that you should reset the logs only if you use an older control
file for restore.
Data Protector Oracle ZDB integration122
To Next Page
Loading...
Need help?
General