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)

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.
SOLUTION
Make sure that the –d <loc> argument entered under rmora_createdb is entered and enclosed
within double quotes (“), and make sure that the shell’s environment variable Internal Field Separator
(IFS) is not set to a comma.
MESSAGE ID
1202
SYMBOLIC NAME
RMO_ERROR_ASM_DISKSTRING
MESSAGE
3PAR1202 ERROR: Could not change asm_diskstring to '%s'.
REASON
When trying to mount a Virtual Copy which contains ASM device(s), the SQL command failed to
change the asm_diskstring parameter in the +ASM instance on the backup server.
SOLUTION
Check the context from screen and/or log file, try to do it manually in +ASM instance on the
backup server, fix the cause for the failure.
MESSAGE ID
1206
SYMBOLIC NAME
RMO_ERROR_UNSUPPORTED_DBROLE
MESSAGE
3PAR1207 ERROR: The database is neither a primary nor physical standby database.
REASON
Recovery Manager for Oracle currently only support creating Virtual Copies for a database that
is either a primary database or a physical standby database.
SOLUTION
Run Recovery Manager for Oracle against a supported database.
MESSAGE ID
1207
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_FRASIZE
MESSAGE
3PAR1207: ERROR: Could not retrieve Flash Recovery Area (FRA) size from the clone parameter
file.
REASON
The command rmora_createdb tries to construct the init.ora file for the cloned database by
modifying the saved init.ora file (could be from the init.ora file directly from the primary
database, or converted from the spfile used by the primary database). The process retrieved
the parameter for db_recovery_file_dest, but failed to retrieve the parameter
db_recovery_file_dest_size.
194 Troubleshooting