You can use BR*Tools for Oracle to perform a whole database reset. BRRECOVER performs the reset.
This section discusses how to perform a whole database reset.
For more information on how to approach a whole database reset, see Whole Database Reset.
· Make sure you have set the necessary BRRECOVER parameters in the initialization profile init<DBSID>.sap, because BRTOOLS uses these when it calls BRRECOVER.
· BRRECOVER calls BRRESTORE as necessary to perform restore functions.
· BRRECOVER calls SQLPLUS as necessary to apply offline redo log files.
1. You start BRGUI or BRTOOLS.
2. You choose Restore and recovery ® Whole database reset.
You can do one of the following:
Ў Set the command line now and run the reset in unattended mode
Ў Wait for BRRECOVER to prompt you during the reset, that is, run the reset in attended mode
We recommend you to normally run the reset in attended mode.
If you are sure of the required entries – for example, for a routine database copy – you can run the reset in unattended mode.
3. If you want to run the reset in unattended mode, you select force in Confirmation mode (confirm).
4. To start the reset, you choose Continue.
BRRECOVER starts the reset. You perform the following steps with BRRECOVER.
If you are running in attended mode, BRRECOVER guides you through the reset, prompting you as necessary.
7. You restore the control files and the offline redo log files. You only restore the offline redo log files if you selected a consistent online backup.
8. You restore data files.
9. If required, you apply an incremental backup.
10. You apply the online redo log – that is, archivelog – files if they were restored in step 7.
11. You open the database.
12. You check the results in the BRRECOVER and BRRESTORE logs:
§ The summary log recov<DBSID>.logdisplays the return code.
§ The detail log v<encoded timestamp>.drs displays the progress.
Ў BRRESTORE logs for the restore functions:
§ The summary log rest<DBSID>.logdisplays the return code
§ The detail log r<encoded timestamp>.<ext> displays the progress.
For more information on how to view the logs, see Showing Logs with BR*Tools.