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

MESSAGE ID
1097
SYMBOLIC NAME
RMO_ERROR_SNAPDEV_NOTFOUND
MESSAGE
3PAR1097: ERROR: Could not find Virtual Copy device for <virtual copy name>.
REASON
The command rmora_mount failed to find the OS device for the specified virtual copy.
SOLUTION
Make sure the configuration on the backup server is supported, such as a multipath configuration,
and make sure related daemons are up. If the host HBA card is not QLogic, Emulex, or iSCSI (refer
to the HP 3PAR configuration matrix), manually add or remove devices from the OS is needed.
MESSAGE ID
1098
SYMBOLIC NAME
RMO_ERROR_OCFS2_VERSION
MESSAGE
3PAR1098: ERROR: Could not decide OCFS2 version.
REASON
During rmora_mount, if Recovery Manager for Oracle discovers that a snapshot file system is
an ocfs2 file system, Recovery Manager for Oracle will try to reset the volume's UUID, using the
ocfs2 command tune.ocfs2, and only supporting ocfs2 1.4.1 or higher release. If the ocfs2
version cannot be determined, the error happens.
SOLUTION
Make sure ocfs2 is installed and configured on the backup server.
MESSAGE ID
1100
SYMBOLIC NAME
RMO_ERROR_DM_SCANEXCLUDE
MESSAGE
3PAR1100: ERROR: The ORACLEASM_SCANEXCLUDE from <parameter> should contain 'sd'.
REASON
In a Linux environment, during rmora_mount Recovery Manager for Oracle checks the asmlib
status on the backup server if it finds out asmlib is being used from the database server. If device
mapper multipath is used, the file /etc/sysconfig/oracleasm should contain the following
lines:
ORACLEASM_SCANORDER="dm"
ORACLEASM_SCANEXCLUDE="sd"
This is to direct asmlib to only scan device mapper devices (dm devices), and not to scan sd format
of devices. This will avoid Oracle asmlib seeing the same disk twice and which can cause unforeseen
problem.
SOLUTION
Modify the specified file and reload the Oracle asmlib.
147