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

rmora_checkconfig is called at the end of creating or modifying a configuration file. It can
also be executed separately. If it finds any check has an unexpected result, the error message will
be displayed.
SOLUTION
Resolve the error, otherwise Recovery Manager for Oracle may not work properly.
MESSAGE ID
1116
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_LDVV
MESSAGE
3PAR1116: ERROR: Could not retrieve logical disks for volume <name>.
REASON
The HP 3PAR CLI command showld failed.
SOLUTION
Check the log file for more information. Make sure TPDSYSNAME and TPDUSERNAME are set
correctly from the configuration file. Make sure the HP 3PAR StoreServ Storage system is working
properly.
MESSAGE ID
1117
SYMBOLIC NAME
RMO_ERROR_RETRIEVE_DEVINFO
MESSAGE
3PAR1117: ERROR: Could not retrieve device information for <name>.
REASON
/dev/sdx failed to retrieve the information for this device, such as VLUN, target, adapter number,
etc.
SOLUTION
Contact customer support for further investigation.
MESSAGE ID
1118
SYMBOLIC NAME
RMO_ERROR_REMOVE_DMDEV
MESSAGE
3PAR1118: ERROR: Could not remove device mapper device <name>.
REASON
Failed to remove the specified device mapper device.
SOLUTION
Make sure the device is not being used by other processes. Most likely the Oracle asmlib or +ASM
instance still holds the resource. Bouncing the +ASM should solve the issue. If it does not resolve
the issue, reboot the backup server and rerun rmora_umount with the -f option.
MESSAGE ID
1127
SYMBOLIC NAME
172 Troubleshooting