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

REASON
Using the command vxvol -g dgname to start up all VxVM volumes failed.
SOLUTION
Check the log file to get more details. Make sure VxVM is in a valid state. Contact customer support
for further investigation.
MESSAGE ID
1259
SYMBOLIC NAME
RMO_ERROR_MOUNT_ASM
MESSAGE
3PAR1259: ERROR: Could not start up the ASM instance or mount the ASM snapshot disk groups.
REASON
Failed to startup the ASM instance or mount the ASM disk groups on the backup server.
SOLUTION
Check the log file to get more details.
MESSAGE ID
1260
SYMBOLIC NAME
RMO_ERROR_MOUNT_ASMDG
MESSAGE
3PAR1260: ERROR: Could not mount one or more ASM disk group(s).
REASON
rmora_mount failed to mount ASM disk group(s).
SOLUTION
Check the log file for more details. Contact customer support for further investigation.
MESSAGE ID
1261
SYMBOLIC NAME
RMO_ERROR_MANUAL_RESCAN
MESSAGE
3PAR1261: ERROR: You must manually scan for snapshot devices, then run rmo_mount again
with the -r option.
REASON
If the host adapter type is not within the supported types (see the HP 3PAR configuration matrix),
Recovery Manager for Oracle will not be able to rescan the volumes to the backup server.
SOLUTION
Manually scan the devices following the specific HBA driver's requirements. Then run rmora_mount
-r
.
MESSAGE ID
1262
SYMBOLIC NAME
RMO_ERROR_DROP_ASMDG
181