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

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_UDUMP_NOTFOUND
MESSAGE
3PAR1202 ERROR: Could not retrieve udump location for database <database name>.
REASON
Failed to retrieve the user_dump_dest value from the specified database.
SOLUTION
Check the alert.log file.
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
.
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
168 Troubleshooting