HP Application Recovery Manager software Integration guide (March 2008)
where Name is the name of the backup specification. For more information on the
omnib command, see its man page or the HP Application Recovery Manager software
command line interface reference.
Restore
Using Application Recovery Manager GUI or CLI, you can restore whole database
and select to recover the database to a certain point in time. You can select to recover
the database using existing archive logs, which must be provided, or you can provide
your own script for database recovery. Database recovery is performed after instant
recovery. If you select to use existing archive logs and if the archive logs are not
available to Oracle Server, an error is reported by the Application Recovery Manager
generated RMAN recovery script and the recovery fails.
Instant recovery and database recovery
See the HP Application Recovery Manager software concepts guide and HP
Application Recovery Manager software administrator's guide for general information
on instant recovery.
The Application Recovery Manager instant recovery functionality is used only to
restore the target volumes on which the database files are located. The database
recovery part is performed after instant recovery and it depends on the recovery
options selected in the GUI.
IMPORTANT:
If the Oracle control file, online redo logs, and SPFILE are on the same source volumes
as datafiles and you enable instant recovery by setting the omnirc variables, note that
the control file, SPFILE, and online redo logs are overwritten during the instant recovery.
Prerequisites
• An instance of Oracle must be created on the system to which you want to restore
the database.
• For recovery:
• The database must be in the STARTUP MOUNT state.
• The Oracle control file that reflects the internal database structure at the time
of backup must be available. If the current control file is lost, use the most
Integration guide 119