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

SOLUTION
Check the log file for more details. Contact customer support for further investigation.
MESSAGE ID
1192
SYMBOLIC NAME
RMO_ERROR_DB_NOTIN_STANDBY
MESSAGE
3PAR1192 ERROR: The database is not in managed recovery mode.
REASON
The database Recovery Manager for Oracle runs against is a physical standby database. However,
the database is not in managed recovery mode and there is no MRP process in the database.
SOLUTION
Check the physical standby database and make sure it is working in managed recovery mode.
MESSAGE ID
1199
SYMBOLIC NAME
RMO_ERROR_INST_NOT_CLOSED
MESSAGE
3PAR1199 ERROR: The following database instances are still not closed: <database instance
name>.
REASON
Creating an offline virtual copy for an RAC database requires all instances in this RAC database
to be offline.
SOLUTION
Shutdown all instances in this RAC database and run the command again.
MESSAGE ID
1200
SYMBOLIC NAME
RMO_ERROR_CREATE_ascii_CTRLFILE
MESSAGE
3PAR1200 ERROR: Could not generate ascii control file for database <database name>.
REASON
Trying to run SQL command alter database backup control file to trace failed.
SOLUTION
Check the Oracle alert.log file. Check if the database is in valid status and check if there is
enough space.
MESSAGE ID
1201
MESSAGE
3PAR1201: ERROR: Could not parse location entered.
REASON
Recovery Manager for Oracle has trouble understanding and parsing the <loc> argument supplied
when user ran the rmora_createdb command.
167