Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

# cd $ORACLE_HOME/lib

■ Take backup of libodm10.so, enter.

# mv libodm10.so libodm10.so.oracle-`date '+%m_%d_%y-%H_%M_%S'`

■ Link libodm10.so with Veritas ODM library, enter:

# ln -s /opt/VRTSodm/lib64/libodm.so libodm10.so

For Oracle11g:

■ Change to the $ORACLE_HOME/lib directory, enter:

# cd $ORACLE_HOME/lib

■ Take backup of libodm11.so, enter.

# mv libodm11.so libodm11.so.oracle-`date '+%m_%d_%y-%H_%M_%S'`

■ Link libodm11.so with Veritas ODM library, enter:

# ln -s /opt/VRTSodm/lib64/libodm.so libodm11.so

Load the ODM module.

# /sbin/init.d/odm start

Start the Oracle database.

To confirm that the Oracle database starts with Veritas Extension for ODM,

the alert log will contain the following text:

Oracle instance running with ODM: Veritas 5.1 ODM Library, Version 2.0

How to prepare existing database storage for Oracle

Disk Manager

Non-Quick I/O files in a VxFS file system work with Oracle Disk Manager without

any changes. The files are found and identified for Oracle Disk Manager I/O by

default. To take full advantage of Oracle Disk Manager datafiles, files should not

be fragmented.

Improving database performance with Veritas Extension for Oracle Disk Manager

How to prepare existing database storage for Oracle Disk Manager