Storage Foundation for Oracle® RAC 7.4.1 Configuration and Upgrade Guide - Solaris

To link the Veritas ODM library

1. Log in as the Oracle user.
2. Change to the $ORACLE_HOME/lib directory:

   $ cd $ORACLE_HOME/lib

3. Back up Oracle's ODM library:

   For Oracle RAC 11g:

   $ mv libodm11.so libodm11.so.oracle-'date +%m_%d_%Y-%H_%M_%S'

   For Oracle RAC 12c:

   $ mv libodm12.so libodm12.so.oracle-'date +%m_%d_%Y-%H_%M_%S'

   For Oracle RAC 18c:

   $ mv libodm18.so libodm18.so.oracle-'date +%m_%d_%Y-%H_%M_%S'

4. Link the Veritas ODM library with Oracle's libodm library:

   For Oracle RAC 11g:

   $ ln -s /usr/lib/sparcv9/libodm.so libodm11.so

   For Oracle 12c:

   $ ln -s /usr/lib/sparcv9/libodm.so libodm12.so
   $ cd $ORACLE_HOME/rdbms/lib
   $ /usr/ccs/bin/make -f ins_rdbms.mk ioracle

   To link the Veritas Extension for ODM with Oracle database 12.1.0.2 manually, see the following Technote:

   https://www.veritas.com/support/en_US/article.TECH225500

   For Oracle RAC 18c, disable direct NFS:

   $ cd $ORACLE_HOME/rdbms/lib 
   $ make -f ins_rdbms.mk dnfs_off OR (make -f ins_rdbms.mk dnfs_off) 
   
   $ cd $ORACLE_HOME/rdbms/lib/odm 
   $ ln -s /usr/lib/sparcv9/libodm.so libodm18.so

5. After the relinking completes, confirm that the correct ODM library is used.

   $ ldd $ORACLE_HOME/bin/oracle | grep odm

   If the library is not linked correctly, no output is displayed. Sometimes, the Oracle ODM library may not be correctly linked with the Veritas ODM library because of the presence of a static ODM library at $ORACLE_HOME/rdbms/lib/libodm10.a. This is a known issue with Oracle.

   To resolve this issue, run the following commands:

   $ cd $ORACLE_HOME/rdbms/lib
   $ mv libodm10.a libodm10.a.backup
   $ /usr/ccs/bin/make -f ins_rdbms.mk ioracle

   Verify that the correct ODM library is used:

   $ ldd $ORACLE_HOME/bin/oracle | grep odm
   libodm10.so =>   /app/oracle/orahome/lib/libodm10.so

   For more information, see the Oracle metalink document: 725903.1