HP 3PAR Application Software Suite for Oracle - Manual (Page 186)

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.
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
3PAR1278: ERROR: The database unique name is different from the virtual copy.
The control file from the backup is not compatible with the current database.
REASON
Trying to execute rmora_restore -c failed with this error if the db_unique_name from the
virtual copy and the current database is different (e.g., the virtual copy is from the standby
database), and the backup method is not RMAN, or the Oracle version is lower than 11g.
SOLUTION
Follow the HP 3PAR Recovery Manager Software for Oracle User's Guide and Recovery Manager
for Oracle CLI manpages to perform supported rmora_restore operations.
MESSAGE ID
1279
SYMBOLIC NAME
RMO_ERROR_ALTHOST
186 Troubleshooting