6. In the Options page:
In User name and User group, specify the user name and password to the
recovery catalog database.
From the Session ID drop-down list, select the Session ID.
For further information, see “Restore, recovery, and duplicate
options” on page 119.
7. Click Restore.
Proceed to restore the control file.
Restoring the control file
The control file contains all the information about the database structure. If the control
file has been lost, you must restore it before you restore any other part of the database.
The database should be in the NoMount state.
Depending on the type of the control file backup, the following types of restore are
possible when restoring the control file:
• Restoring from Data Protector managed control file backup (CONTROLFILE FROM
DP MANAGED BACKUP)
The control file was backed up automatically by ob2rman.pl at the end of a
backup session, unless the option Disable Data Protector managed
control file backup was selected.
The recovery catalog is not required for this restore option.
The control files (ctrlDB_NAME.dbf) are restored to:
Windows:
Data_Protector_home\tmp
HP-UX, Solaris:
/var/opt/omni/tmp
After the restore, run the following script:
run {
allocate channel 'dev0' type disk;
restore controlfile from 'TMP_FILENAME';
release channel 'dev0';
}
Where TMP_FILENAME is the location to which the file was restored.
• Restoring from RMAN backup set (CONTROLFILE FROM RMAN BACKUPSET)
The recovery catalog is required.
A backup session can contain more than one type of the control file backup.
Data Protector Oracle ZDB integration108
To Next Page
Loading...
Need help?
General