HP Data Protector A.06.11 Integration Manual page 101

The control file was automatically backed up by RMAN and the recovery catalog
is not available.
IMPORTANT:
Ensure that you have properly configured the RMAN autobackup and that the
correct backup version is available. If the RMAN autobackup session is not found
during the restore, the procedure is aborted. See the Oracle documentation on
how to set up RMAN AUTOBACKUP.
• Restoring from RMAN backup set (CONTROLFILE FROM RMAN BACKUPSET)
The recovery catalog is required.
Oracle Data Guard (10g/1 1g only): Restoring standby control file from RMAN
•
backup set (STANDBY CONTROL FILE FROM RMAN BACKUPSET)
If you restore a standby database (not using duplication), you must restore this
type of control file.
This type of restore is available only in Oracle 10g/1 1g standby configurations
and if you selected the CONTROL FILE FOR STANDBY database object in the
backup specification.
A backup session can contain more than one type of the control file backup.
To restore the control file:
1. Open the sqlplus window and put the database in the nomount state. See
"Changing the database
2. In the Data Protector GUI, switch to the Restore context.
3. Under Restore Objects, expand Oracle Server, expand the client on which the
database, for which you want to restore the control file, resides, and then click
the database.
4. In the Restore Action drop-down list, select Perform RMAN Repository Restore.
In the Results area, select the control file for restore.
5. In the Options page, from the Client drop-down list, select the client on which
the Data Protector Oracle integration agent (ob2rman.pl) will be started. To
restore the control file to a different database than it is selected, click Settings
and specify the login information for the target database.
Set the other restore options. See
options" on page 114 for information.
state" on page 97.
"Restore, recovery, and duplicate
Integration guide for Oracle and SAP 101