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

SOLUTION
Make sure TPDSYSNAME and TPDUSERNAME to access the specified HP 3PAR StoreServ Storage
system are correct. Make sure the Remote Copy is set up properly.
MESSAGE ID
1295
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_RCVV
MESSAGE
3PAR1295: ERROR: Could not retrieve Remote Copy volumes from HP 3PAR StoreServ Storage
system .
REASON
The HP 3PAR CLI command showrcopy failed to retrieve the Remote Copy volumes information.
SOLUTION
Make sure TPDSYSNAME and TPDUSERNAME to access the specified HP 3PAR StoreServ Storage
system are correct. Make sure the Remote Copy and Remote copy groups are set up properly.
MESSAGE ID
1301
SYMBOLIC NAME
RMO_ERROR_CLONEDB_UP
MESSAGE
3PAR1301: ERROR: The clone database instance 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 is in use by the database .
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
214 Troubleshooting