HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

1. Cloning database is only available to online or offline Virtual Copies.
2. Restore files which requires later recovery operations cannot be a archive log only Virtual
Copy, should be one of the online or offline types.
3. There is no need to restore archive log files using RMAN as RMAN recovery will automatically
restore necessary archive log files.
MESSAGE ID
1276
SYMBOLIC NAME
RMO_ERROR_ARCHLOG_RESTORE
MESSAGE
3PAR1276: ERROR: Archive logs will be restored automatically during media recovery using
Oracle RMAN.
REASON
Trying to restore archive log files using RMAN fails.
SOLUTION
There is no need to restore archive log files alone. RMAN will automatically restore necessary
archive log files during media recovery.
An example to use RMAN to restore necessary archive log files and recover the database:
rman target / catalog <rman_user>/<password>@<catalog_db>
RUN {
ALLOCATE CHANNEL c1 TYPE SBT_TAPE;
SEND 'NB_ORA_CLIENT=RMO backup server name';
RECOVER DATABASE;
MESSAGE ID
1277
SYMBOLIC NAME
RMO_ERROR_RESTORE_DIFFERENT_DB
MESSAGE
3PAR1277: ERROR: Restoring to a different database is not supported.
REASON
The command rmora_restore returns this error in the following two cases:
1. If the alternate SID is different from the SID in the Virtual Copy, and the database to be restored
to is the primary database (not standby database).
2. The db_name parameter from the database to restore to and the one from the Virtual Copy
are different.
SOLUTION
1. The alternate SID option can be used to specify the Oracle SID of the production database if
it is different from the SID of the standby database from which the backup image is used for
restoring.
2. Restore the Virtual Copy to a database with the same db_name.
MESSAGE ID
1278
SYMBOLIC NAME
RMO_ERROR_RESTORE_DIFFERENT_DB_UNIQUE_NAME
MESSAGE
212 Troubleshooting