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)

SOLUTION
Check the primary database and make sure the two parameters are set correctly. You can manually
correct the problem in the init.ora file saved in the timestamp directory and perform
rmora_createdb again.
MESSAGE ID
1208
SYMBOLIC NAME
RMO_ERROR_ARCHLOG_GAP
MESSAGE
3PAR1208 ERROR: Archive log gap exists between the primary and standby database.
REASON
Recovery Manager for Oracle runs against a physical standby database. Trying to create an online
or archive log only Virtual Copy fails because there is a gap for archive log files.
SOLUTION
Transfer the archive log files from the database server to the physical standby database.
MESSAGE ID
1211
SYMBOLIC NAME
RMO_ERROR_QUIESCE_STBYDB
MESSAGE
3PAR1211 ERROR: Could not stop redo apply process for database '%s'.
REASON
Trying to stop the managed recovery process for the physical standby database failed. The SQL
command used is: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL.
SOLUTION
Check the alert.log file and make sure the physical standby database is valid.
MESSAGE ID
1212
SYMBOLIC NAME
RMO_ERROR_UNQUIESCE_STBYDB
MESSAGE
3PAR1212 ERROR: Could not restart redo apply process for database <database name>.
REASON
The SQL command ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT
FROM SESSION failed.
SOLUTION
Check the alert.log file for the physical standby database and make sure it is in the valid
state.
MESSAGE ID
1215
SYMBOLIC NAME
RMO_ERROR_UNRECOGNIZED_UUID
MESSAGE
195