Oracle Database 11g Release 2 Real Application Clusters with SLVM/RAW on HP-UX Installation Cookbook, September 2010

– Import the volume group:

cycle# vgimport –v –s -N –m /tmp/scripts/mapfile /dev/vg_rac

Note: the -N option is for HP-UX 11.31 agile addressing

Note: The minor number has to be the same as on the other node.

– Check to see if devices are imported:

cycle# strings /etc/lvmtab

• Disable automatic volume group activation on all cluster nodes by setting AUTO_VG_ACTIVATE to

0 in file /etc/lvmrc. This ensures that shared volume group vg_rac is not automatically activated at

system boot time. In case you need to have any other volume groups activated, you need to

explicitly list them at the customized volume group activation section.

• It is recommended best practice to create symbolic links for each of these raw files on all systems of

your RAC cluster. Example as follows.

bike/cycle# cd /oracle/RAC/ (directory where you want to have the links)

bike/cycle# ln -s /dev/vg_rac/<dbname>_system_1300m

bike/cycle# ln -s /dev/vg_rac/<dbname>_sysaux_1300m

• Change the permissions of the database volume group vg_rac to 775, and change the permissions

of all raw logical volumes to 660 and the owner to oracle:oinstall.

bike/cycle# chmod 775 /dev/vg_rac

bike/cycle# chmod 660 /dev/vg_rac/r*

bike/cycle# chown oracle:dba /dev/vg_rac/r*

• Change the permissions of the OCR and voting disk logical volumes:

bike/cycle# chown oracle:dba /dev/vg_oracle/r*

bike/cycle# chmod 640 /dev/vg_rac/roar_ocr_1024m

bike/cycle# chmod 660 /dev/vg_rac/roar_vote_512m

Serviceguard/SGeRAC Configuration

After SLV

M set-up, you can now start the Serviceguard cluster configuration.

In general, you can configure your Serviceguard cluster using lock disk or quorum server. We

describe here the cluster lock disk set-up. Since we have already configured one volume group for the

entire RAC cluster vg_rac, we use vg_rac for the lock volume as well.

1. This step is applicable only, if you want to use lvm cluster lock disk. Skip this step, if you are

planning to use Quorum Server and Lock LUN. Activate the lock disk on the configuration node

ONLY. Lock volume can only be activated on the node where the cmapplyconf command is issued

so that the lock disk can be initialized accordingly.

bike# vgchange -a y /dev/vg_rac

2. Create a cluster configuration template:

bike# cmquerycl –n bike –n cycle –v –C /etc/cmcluster/rac.asc

3. Edit the cluster configuration file (rac.asc).

Make the necessary changes to this file for your cluster. For example, change the Cluster Name adjust

the heartbeat interval and node timeout to prevent unexpected failovers due to DLM traffic. Configure

all shared volume groups that you are using for RAC, including the volume group that contains the

Oracle CRS files using the parameter OPS_VOLUME_GROUP at the bottom of the file. Also, ensure to

have the right LAN interfaces configured for the SG heartbeat.

• Check the cluster configuration:

bike# cmcheckconf -v -C rac.asc