To verify that Oracle Disk Manager is configured

1. Verify that the ODM feature is included in the license:

   # /opt/VRTS/bin/vxlicrep | grep ODM
   

   The output verifies that ODM is enabled.

   Note:

   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.

2. Check that the VRTSodm fileset is installed:

   # lslpp -L VRTSodm
   Fileset			Level		 State  Type  Description (Uninstaller)
   ------------------------------------------------------------
   VRTSodm			5.1.x.x			C	F		Veritas Extension for
   																									Oracle Disk Manager
   
   State codes:
   A -- Applied.
   B -- Broken.
   C -- Committed.
   O -- Obsolete.  (partially migrated to newer version)
   ? -- Inconsistent State...Run lppchk -v.
   
   
   
   Type codes:
   F -- Installp Fileset
   P -- Product
   C -- Component
   T -- Feature
   R -- RPM Package

3. Check that 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

1. Start the Oracle database.
2. Check that the instance is using the Oracle Disk Manager function:

   # cat /dev/odm/stats
   # echo $?
   0

3. Verify that the Oracle Disk Manager is loaded:

   You can use the genkld or the genkex commands:

   # genkld | grep odm
   or
   # genkex | grep odm
   

4. In the Oracle 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, 
   Version 2.0