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

MESSAGE ID
1301
SYMBOLIC NAME
RMO_ERROR_CLONEDB_UP
MESSAGE
3PAR1301: ERROR: The clone database instance <name> is currently running.
REASON
Trying to clone a database with the specified name failed, as a database with same instance name
is already up and running.
SOLUTION
If the running database was cloned using a virtual copy from a different database, change the
rmora_createdb
parameter to use a new Oracle SID.
MESSAGE ID
1302
SYMBOLIC NAME
RMO_ERROR_VC_IN_USE
MESSAGE
3PAR1302: ERROR: The virtual copy <name> is in use by the database <name>.
REASON
Trying to clone a database from the specified virtual copy failed, as the virtual copy was used to
clone a different Oracle database already.
SOLUTION
If the existing cloned database is no longer used, remove the database and read-write virtual copy
in order to clone a point-in-time consistent database from the read-only virtual copy again. This
can be done by executing rmora_removedb and rmora_umount commands sequentially.
MESSAGE ID
1303
SYMBOLIC NAME
RMO_ERROR_OPEN_DB
MESSAGE
3PAR1303: ERROR: Could not open database instance <name>.
REASON
The operation to clone a database failed. A cloned database using the same virtual copy already
exists, Recovery Manager for Oracle failed to open the existing clone database.
SOLUTION
Check alert.log to find more details.
MESSAGE ID
1304
SYMBOLIC NAME
RMO_ERROR_CFILEDG_NOTFOUND
MESSAGE
3PAR1304: ERROR: Control file ASM disk group <name> not found.
REASON
188 Troubleshooting