Restoring Control Files

You restore the control files when using BRRECOVER to perform:

For a whole database reset, you also restore the online redo log files, but only if you selected an offline backup.

Note Note

Whereas a whole database reset always restores the control files, a database PIT recovery only restores them if they:

End of the note.

This procedure calls BRRESTORE to restore the control files and - if required for whole database reset - the online redo log files.

You can repeat this phase if a BRRESTORE call has failed.

Set the required options:

Menu Entry	Equivalent BRRESTORE Command Option
BRRESTORE profile (profile)	-p\|-profile
BRBACKUP run (backup)	-b\|-backup\|b1\|backup1
Restore device type (device)	-d\|-device
BACKINT/Mount profile (parfile)	-r\|-parfile
Files for restore (mode)	-m\|-mode [,archive_logs]
Confirmation mode (confirm)	-c\|-confirm
Query mode (query)	-q\|-query
Compression mode (compress)	-k\|-compress
Additional output (output)	-o\|-output
Message language (language)	-l\|-language
BRRESTORE command line (command)	This shows you the BRRESTORE command that is to be executed using the current settings.

Note Note

Restore device type (device) is taken from the device type used for the selected backup.

Files for restore (mode) refers to the Oracle file ID or the keyword archive_logs. The files for restore varies:

For the control files restore, a dummy file ID, 0, is used.
For the restore of online redo log files from an offline consistent backup (only relevant for whole database reset, as described above), a dummy file ID of 00 is used.

End of the note.

To start the restore with the selected options, choose Continue.
Check the results in the BRRESTORE logs:
- The summary log rest<DBSID>.log displays the return code.
- The detail log r<encoded timestamp>.rsb displays the progress.
For more information on how to view the logs, see Showing Profiles and Logs with BR*Tools.