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)

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
During rmora_createdb process, the error occurs when:
• A non-default clone location (option -d) was specified to clone the database, and
• At least one of the clone locations is an ASM disk group, which means the control file will
reside on one of the ASM disk groups on the backup server, and
• The ASM instance on the backup server does not contain the disk group for the control file.
SOLUTION
Before executing rmora_createdb, make sure the ASM instance on the backup server has the
ASM disk group that will hold control files exists and is mounted.
MESSAGE ID
1306
SYMBOLIC NAME
RMO_ERROR_SCAN_DEV
MESSAGE
3PAR1306: ERROR: Failed to scan snapshot OS devices.
REASON
During rmora_mount or mora_umount, the operation trying to find the devices included in a
Virtual Copy failed.
SOLUTION
It could be caused by previous failed Virtual Copy rmora_mount or mora_umount operations,
try the command again, if still fails, try to reboot the backup server to clean up the stale devices.
MESSAGE ID
1307
SYMBOLIC NAME
RMO_ERROR_MULTIPATHD
MESSAGE
3PAR1307: ERROR: multipathd daemon is not running.
REASON
215