Verifying that Oracle Disk Manager is configured
Before verifying that Oracle Disk Manager is configured, make sure that the following conditions are met:
If you are using Oracle 10g,
$ORACLE_HOME/lib/libodm10.so is linked
If you are using Oracle 11g, $ORACLE_HOME/lib/libodm11.so
is linked to /opt/VRTSodm/lib/libodm64.so.
The VRTSdbed license
must be valid.
The VRTSodm package
must be installed.
To verify that Oracle Disk Manager is configured
Verify that the ODM feature is included in the license:
# /opt/VRTS/bin/vxlicrep | grep ODM
The output verifies that ODM is enabled.
Verify that the license key containing the ODM feature is not expired. If the license key has expired, you will not be able to use the ODM feature.
Check that the
VRTSodm package is installed:
# lslpp -L VRTSodm
Fileset Level State Type Description (Uninstaller)
VRTSodm 5.1.x.x C F Veritas Extension for
Oracle Disk Manager
A -- Applied.
B -- Broken.
C -- Committed.
O -- Obsolete. (partially migrated to newer version)
? -- Inconsistent State...Run lppchk -v.
F -- Installp Fileset
P -- Product
C -- Component
T -- Feature
R -- RPM Package
libodm64.so is present.
# ls -lL /opt/VRTSodm/lib/libodm64.so
-r-xr-xr-x 1 bin bin 103500 Aug 16 08:42 /opt/VRTSodm/lib/libodm64.so
To verify that Oracle Disk Manager is running
Start the Oracle database.
Check that the instance is using the Oracle Disk Manager function:
# cat /dev/odm/stats
# echo $?
Verify that the Oracle Disk Manager is loaded:
You can use the genkld or the genkex commands:
# genkld | grep odm
# genkex | grep odm
In the alert log, verify the Oracle instance is running. The log should contain output similar to the following:
Oracle instance running with ODM: Veritas 5.1.100.00 ODM Library,