Using Serviceguard Extension for RAC, 6th Edition, April 2008

IMPORTANT: After creating these files, use the vxedit command to change the

ownership of the raw volume files to oracle and the group membership to dba, and

to change the permissions to 660. Example:

# cd /dev/vx/rdsk/ops_dg

# vxedit -g ops_dg set user=oracle *

# vxedit -g ops_dg set group=dba *

# vxedit -g ops_dg set mode=660 *

The logical volumes are now available on the primary node, and the raw logical volume

names can now be used by the Oracle DBA.

Mirror Detachment Policies with CVM

The required CVM disk mirror detachment policy is ‘global’, which means that as soon

as one node cannot see a specific mirror copy (plex), all nodes cannot see it as well. The

alternate policy is ‘local’, which means that if one node cannot see a specific mirror

copy, then CVM will deactivate access to the volume for that node only.

This policy can be re-set on a disk group basis by using the vxedit command, as

follows:

# vxedit set diskdetpolicy=global <DiskGroupName>

NOTE: The specific commands for creating mirrored and multi-path storage using

CVM are described in the HP-UX documentation for the Veritas Volume Manager.

Using CVM 3.x

This section has information on how to prepare the cluster with CVM 3.x (on HP-UX

releases that support Veritas CFS and CVM; see “About Veritas CFS and CVM from

Symantec” (page 25)).

Preparing the Cluster for Use with CVM 3.x

In order to use the Veritas Cluster Volume Manager (CVM) version 3.5, the cluster must

be running with a special CVM package. This means that the cluster must already be

configured and running before you create disk groups.

NOTE: Cluster configuration is described in the previous section.

To prepare the cluster for CVM disk group configuration, you need to ensure that only

one heartbeat subnet is configured. Then use the following command, which creates

the special package that communicates cluster information to CVM:

# cmapplyconf -P /etc/cmcluster/cvm/VxVM-CVM-pkg.conf

120 Serviceguard Configuration for Oracle 9i RAC