Performing Flashback Database
You use this procedure when using BRRECOVER to perform flashback database during:
BRRECOVER first remounts – that is, closes and again mounts – the database to refresh the views V$DATAFILE, V$RECOVER_FILE, and V$RECOVERY_STATUS.
BRRECOVER checks whether there are any data files not online. If so, it recommends to set them online.
BRRECOVER displays a list of the redo log files to be automatically applied by Oracle during the flashback database.
Note
Some offline redo log files might be present on multiple media sources. For example, a file might be present on disk and on tape. BRRECOVER normally uses the most accessible version of the file, unless you specify otherwise. In this example, it would use the disk version of the file.
If required, change the default options for Oracle to automatically apply the offline redo log files:
Menu Entry |
Meaning |
|---|---|
|
First offline redo log to apply |
|
Last offline redo log to apply |
If a restore is necessary, set the required options:
Menu Entry |
Equivalent BRRESTORE Command Options |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Choose Continue
.
If required, alter the Database flashback target
for the flashback:
Menu Entry |
Equivalent BRRECOVER Command Options |
|---|---|
|
|
|
The SQL command that is to be executed using the current settings. For more information, see your Oracle SQL documentation. |
For whole database reset, you can change the restore point
.
For database point-in-time recovery, you can change the timestamp
.
Choose Continue
.
BRRECOVER performs flashback database.
Check the results in the BRRESTORE and BRRECOVER logs. The detail
log r<encoded timestamp>.rsa
displays the progress for restoring the offline redo log files.
For more information on how to view the logs, see Showing Profiles and Logs with BR*Tools.