< Previous  | TOC | Index | Next  >

Configuring CVM and Oracle service groups manually

You can edit the main.cf file directly to configure the CVM and Oracle service groups.

 To configure CVM and Oracle service groups manually

1. Log in as superuser to one system.
2. Save your existing configuration to prevent any changes while you modify main.cf:

   # haconf -dump -makero

3. Ensure VCS is not running while you edit main.cf by using the hastop command to stop the VCS engine on all systems and leave the resources available:

   # hastop -all -force

4. Make a backup copy of the main.cf file:

   # cd /etc/VRTSvcs/conf/config

   # cp main.cf main.orig

5. Using vi or another text editor, edit the main.cf file to modify the cvm service group.

   Review the guidelines in the example configuration to modify the CVM service group.

   See Configuring CVM group with Oracle binaries installed locally

6. Using vi or another text editor, edit the main.cf file to create Oracle service groups.

   See Creating Oracle service group in the main.cf file

Configuring CVM group with Oracle binaries installed locally

Review the illustration that depicts the example scenario.

See CVM Group with Oracle Installed Locally; SRVM on Shared File System; Host IP Used

Modifying the CVM service group in the main.cf file

The cvm service group is created during the installation of Storage Foundation for Oracle RAC. After installation, the main.cf file resembles the example shown in Sample main.cf file after SF Oracle RAC installation. Because Oracle had not been installed, the cvm service group includes only resources for the CFSfsckd daemon and CVMCluster resource.

You must modify the cvm service group to add the Netlsnr, Mount, Disk Group, CVMVolDg, and CFSMount resources to the configuration. You can refer to Sample VCS configuration files for SF Oracle RAC, to see a complete example of how a cvm group is configured.

1. Make sure the cvm group has the group Parallel attribute set to 1.

   Typically this is already done during installation.

   .

   group cvm (

   SystemList = { galaxy = 0, nebula = 1 }

   AutoFailOver = 0

   Parallel = 1

   AutoStartList = { galaxy, nebula }

   )

   .

2. Define the Mount and DiskGroup resources for use by the Oracle binaries.

   The VCS bundled Mount and DiskGroup agents are described in Veritas Cluster Server Bundled Agents Reference Guide.

   .

   Mount orabin_mnt (

   MountPoint = "/prod/u01"

   BlockDevice = "/dev/vx/dsk/ora_bin_dg/ora_bin"

   FSType = vxfs FsckOpt = "-n"

   )

   DiskGroup orabin_dg (

   DiskGroup = ora_bin_dg

   StartVolumes = 0

   StopVolumes = 0

   )

   .

   .

3. Define the Netlsnr resource.

   The Netlsnr listener agent is described in detail in the Veritas High Availability Agent for Oracle Installation and Configuration Guide. Note that the Listener attribute is localized for each node.

   .

   Netlsnr LISTENER (

   Owner = oracle

   Home = "/oracle/orahome"

   TnsAdmin = "/oracle/orahome/network/admin"

   MonScript = "./bin/Netlsnr/LsnrTest.pl"

   Listener @galaxy = LISTENER_a

   Listener @nebula = LISTENER_b

   EnvFile = "/opt/VRTSvcs/bin/Netlsnr/envfile"

   )

   .

4. You must configure the CVMVolDg and CFSMount resources in the cvm group for the SRVM disk group configured on shared storage.

   Refer to the appendix SF Oracle RAC agents for description of CVMVolDg and CFSMount agents.

   .

   .

   CFSMount ora_srv_mnt (

   Critical = 0

   MountPoint = "/orasrv"

   BlockDevice = "/dev/vx/dsk/orasrv_dg/srvm_vol"

   Primary = galaxy

   )

   CVMVolDg srvm_vol_dg (

   CVMDiskGroup = orasrv_dg

   CVMVolume = { "srvmvol" }

   CVMActivation = sw

   )

   .

   .

5. Define the dependencies of resources in the group.

   The Netlsnr resource requires the Mount resource. The Mount resource requires DiskGroup resource. The CFSMount resource depends on the CVMVolDg resource, which, in turn, requires the CVMCluster resource, which autoimports the shared storage and establishes GAB communications within the cluster. The CFSMount resource also requires the CFSfsckd resource daemon, vxfsckd, used by the cluster file system. The CVMCluster resource depends on the CVMVxconfigd daemon to maintain the disk and disk group configuration.

   .

   .

   LISTENER requires orabin_mnt

   orabin_mnt requires orabin_dg

   srvm_mnt requires srvm_vol_dg

   srvm_mnt requires vxfsckd

   srvm_vol_dg requires cvm_clus

   cvm_clus requires cvm_vxconfigd

   .

   .

Creating Oracle service group in the main.cf file

For a complete description of the VCS Oracle enterprise agent, refer to the document, Veritas High Availability Agent for Oracle Installation and Configuration Guide. That document includes instructions for configuring the Oracle and Netlsnr agents.

The VCS Enterprise Agent for Oracle version 4.1 is installed when you run the installer script. When you refer to the Veritas High Availability Agent for Oracle Installation and Configuration Guide, ignore the steps described in the section "Installing the Agent Software."

1. Using the Sample VCS configuration files for SF Oracle RAC as an example, add a service group to contain the resources for an Oracle database. For example, add the group oradb1_grp. Make sure you assign the Parallel attribute a value of 1.

   .

   group oradb1_grp (

   SystemList = { galaxy = 0, nebula = 1 }

   AutoFailOver = 0

   Parallel = 1

   AutoStartList = { galaxy, nebula }

   )

   .

   .

2. Create the CVMVolDg and CFSMount resource definitions. See SF Oracle RAC agents for a description of these agents and their attributes.

   .

   .

   CVMVolDg ora_db1_voldg (

   CVMDiskGroup = oradb1dg

   CVMVolume = { "oradb1vol" }

   CVMActivation = sw

   )

   CFSMount ora_db1_mnt (

   MountPoint = "/oradb1"

   BlockDevice = "/dev/vx/dsk/oradb1dg/oradb1vol"

   Primary = galaxy

   )

   .

   .

3. Define the Oracle database resource. Refer to the Veritas High Availability Agent for Oracle Installation and Configuration Guide for information on the VCS enterprise agent for Oracle. Note that the Oracle attributes Sid, Pfile, and Table attributes must be set locally, that is, they must be defined for each cluster system.

   .

   .

   Oracle VRT (

   Sid @galaxy = VRT1

   Sid @nebula = VRT2

   Owner = oracle

   Home = "/oracle/orahome"

   Pfile @galaxy = "/oracle/orahome/dbs/initVRT1.ora"

   Pfile @nebula = "/oracle/orahome/dbs/initVRT2.ora"

   User = scott

   Pword = tiger

   Table @galaxy = vcstable_galaxy

   Table @nebula = vcstable_nebula

   MonScript = "./bin/Oracle/SqlTest.pl"

   AutoEndBkup = 1

   EnvFile = "/opt/VRTSvcs/bin/Oracle/envfile"

   )

   .

   .

4. Define the dependencies for the Oracle service group. Note that the Oracle database group is specified to require the cvm group, and that the required dependency is defined as "online local firm," meaning that the cvm group must be online and remain online on a system before the Oracle group can come online on the same system. Refer to the Veritas Cluster Server User's Guide for a description of group dependencies.

   .

   .

   requires group cvm online local firm

   oradb1_mnt requires oradb1_voldg

   VRT requires oradb1_mnt

   .

   .

See the Sample VCS configuration files for SF Oracle RAC for a complete example. You can also find the complete file in /etc/VRTSvcs/conf/sample_rac/main.cf.

When you complete editing the main.cf file, see the next section, Saving and checking the configuration.

Saving and checking the configuration

When you complete editing the main.cf file to configure the CVM and Oracle service groups, verify the new configuration.

 To verify the configuration

1. Save and close the main.cf file.
2. Verify the syntax of the file /etc/VRTSvcs/conf/config/main.cf:

   # hacf -verify /etc/VRTSvcs/conf/config

3. Start the VCS engine on one system:

   hastart

4. Type the command hastatus:

   # hastatus

5. When "LOCAL_BUILD" is listed in the message column, start VCS on the other system:

   # hastart

6. Verify that the service group resources are brought online. On one system, enter:

   # hagrp -display

Additional RAC processes monitored by the VCS Oracle agent

For shallow monitoring, the VCS Oracle agent monitors the Oracle9i RAC processes ora_lmon and ora_lmd, in addition to the processes ora_dbw, ora_smon, ora_pmon, and ora_lgwr.

Attributes of CVM, Oracle groups defined as local

The following table lists attributes that must be defined as local for the CVM and Oracle service groups (note that each attribute has string-scalar as the type and dimension).

If other attributes for the Oracle resource differ for various RAC instances, define them locally as well. These other attributes may include the Oracle resource attributes User, PWord, the CVMVolDg resource attribute CVMActivation, and others.

Modifying the VCS configuration

For additional information and instructions on modifying the VCS configuration, refer to the Veritas Cluster Server User's Guide.

Location of VCS and Oracle agent log files

On all cluster nodes, look at the following log files for any errors or status messages:

/var/VRTSvcs/log/engine_A.log

/var/VRTSvcs/log/Oracle_A.log

/var/VRTSvcs/log/Netlsnr_A.log

When large amounts of data are written, multiple log files may be required. For example, engine_B.log, engine_C.log, and so on, may be required. The engine_A.log contains the most recent data.