How to Configure Oracle Database Access

1. Configure the disk devices for use by your volume manager.

   For more information, see the appendix for your volume manager in the Sun Cluster 3.0 Installation Guide.

2. If you are using Solstice DiskSuite, set up UFS logging or raw mirrored meta devices on all the nodes that are running Sun Cluster HA for Oracle.

   If you are using raw devices to contain the databases, change the owner, group, and mode of each of the raw mirrored meta devices and verify the changes. If you are not using raw devices, skip this step. Instructions for configuring raw devices are provided in the Sun Cluster 3.0 Installation Guide.

   If you are creating raw devices, type the following commands for each device on each node that can master the Oracle resource group:

   # chown oracle_id /dev/md/disk_device_group/rdsk/dn # chgrp dba_id /dev/md/disk_device_group/rdsk/dn # chmod 600 /dev/md/disk_device_group/rdsk/dn

   Verify that the changes have taken effect.

   # ls -lL /dev/md/disk_device_group/rdsk/dn

3. If you are using VERITAS Volume Manager, set up UFS logs or raw devices on all the nodes.

   For information about Solaris UFS logging, see the mount_ufs(1M) man page and the Solaris Transition Guide. If you are using raw devices to contain the databases, change the owner, group, and mode of each device. If not, skip this step.

   If you are creating raw devices, type the following command for each raw device:

   # vxedit -g disk_device_group set user=oracle_id \ group=dba mode=600 volume_name

   Verify that the changes have taken effect.

   # ls -lL /dev/vx/rdsk/disk_device_group/volume_name

   Next, re-register the disk device group with the cluster. This step is necessary to keep the VxVM namespace consistent throughout the cluster. If you are using Solstice DiskSuite, you can skip this step.

   # scconf -c -D name=disk_device_group