How To Add Oracle File System To A Vcs Service Group Step By Step

Configuring CVM and Oracle service groups manually

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

To configure CVM and Oracle service groups manually

Log in equally superuser to 1 organisation.
Save your existing configuration to forestall any changes while you modify chief.cf:
# haconf -dump -makero
Ensure VCS is not running while y'all edit principal.cf by using the hastop command to end the VCS engine on all systems and go out the resources available:
# hastop -all -force
Make a backup copy of the main.cf file:
# cd /etc/VRTSvcs/conf/config

# cp main.cf main.orig
Using vi or another text editor, edit the main.cf file to alter 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
Using vi or another text editor, edit the master.cf file to create Oracle service groups.
See Creating Oracle service grouping in the chief.cf file

Configuring CVM group with Oracle binaries installed locally

Review the illustration that depicts the instance scenario.

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

Modifying the CVM service group in the main.cf file

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

You must change the cvm service grouping to add the Netlsnr, Mount, Disk Grouping, 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 grouping is configured.

Make certain the cvm grouping has the group Parallel attribute set to 1.
Typically this is already done during installation.

.

group cvm (

SystemList = { galaxy = 0, nebula = one }

AutoFailOver = 0

Parallel = 1

AutoStartList = { galaxy, nebula }

)

.
Define the Mountain and DiskGroup resources for use by the Oracle binaries.
The VCS arranged 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 = "-north"

)

DiskGroup orabin_dg (

DiskGroup = ora_bin_dg

StartVolumes = 0

StopVolumes = 0

)

.

.
Define the Netlsnr resources.
The Netlsnr listener agent is described in particular 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

Dwelling = "/oracle/orahome"

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

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

Listener @milky way = LISTENER_a

Listener @nebula = LISTENER_b

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

)

.
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 clarification of CVMVolDg and CFSMount agents.

.

.

CFSMount ora_srv_mnt (

Critical = 0

MountPoint = "/orasrv"

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

Principal = galaxy

)

CVMVolDg srvm_vol_dg (

CVMDiskGroup = orasrv_dg

CVMVolume = { "srvmvol" }

CVMActivation = sw

)

.

.
Ascertain the dependencies of resources in the group.
The Netlsnr resource requires the Mount resource. The Mountain 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 resources also requires the CFSfsckd resources daemon, vxfsckd, used by the cluster file system. The CVMCluster resources 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 consummate description of the VCS Oracle enterprise amanuensis, refer to the certificate, Veritas High Availability Agent for Oracle Installation and Configuration Guide. That document includes instructions for configuring the Oracle and Netlsnr agents.

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

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

group oradb1_grp (

SystemList = { galaxy = 0, nebula = i }

AutoFailOver = 0

Parallel = 1

AutoStartList = { galaxy, nebula }

)

.

.
Create the CVMVolDg and CFSMount resource definitions. Run into SF Oracle RAC agents for a clarification 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 = milky way

)

.

.
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. Notation that the Oracle attributes Sid, Pfile, and Table attributes must exist set up locally, that is, they must exist defined for each cluster system.
.

.

Oracle VRT (

Sid @galaxy = VRT1

Sid @nebula = VRT2

Possessor = oracle

Abode = "/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 = ane

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

)

.

.
Define the dependencies for the Oracle service group. Note that the Oracle database group is specified to crave 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 tin come online on the same system. Refer to the Veritas Cluster Server User'due south Guide for a clarification of group dependencies.
.

.

requires group cvm online local business firm

oradb1_mnt requires oradb1_voldg

VRT requires oradb1_mnt

.

.

Run into the Sample VCS configuration files for SF Oracle RAC for a complete example. You lot can also detect the consummate file in /etc/VRTSvcs/conf/sample_rac/master.cf.

When you consummate editing the main.cf file, run across the next department, Saving and checking the configuration.

Saving and checking the configuration

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

To verify the configuration

Save and shut the main.cf file.
Verify the syntax of the file /etc/VRTSvcs/conf/config/master.cf:
# hacf -verify /etc/VRTSvcs/conf/config
Start the VCS engine on one arrangement:
hastart
Type the command hastatus:
# hastatus
When "LOCAL_BUILD" is listed in the message column, commencement VCS on the other system:
# hastart
Verify that the service group resources are brought online. On one system, enter:
# hagrp -display

Additional RAC processes monitored by the VCS Oracle amanuensis

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

Attributes of CVM, Oracle groups divers equally local

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

Resource	Attribute	Definition
IP	Accost	The virtual IP address (non the base of operations IP address) associated with the interface. For example: Address @sysa = "192.2.forty.21" Accost @sysb = "192.2.40.22"
Netlsnr	Listener	The name of the Listener. For example: Listener @sysa = LISTENER_a Listener @sysb = LISTENER_b
Oracle	Sid	The variable $ORACLE_SID represents the Oracle organization ID. For example, if the SIDs for two systems, `sysa` and `sysb`, are VRT1 and VRT2 respectively, their definitions would be: Sid @sysa = VRT1 Sid @sysb = VRT2
Oracle	Pfile	The parameter file: `$ORACLE_HOME/dbs/init$ORACLE_SID.ora`. For example: Pfile @sysa = "/oracle/VRT/dbs/initVRT1.ora" Pfile @sysb = "/oracle/VRT/dbs/initVRT2.ora"
Oracle	Table	The table used for in-depth monitoring past `User/PWord` on each cluster node. For instance: Table @sysa = vcstable_sysa Table @sysb = vcstable_sysb Symantec does not recommend using the same table on all Oracle instances. Using the same tabular array generates VCSIPC traffic and could crusade conflicts betwixt the Oracle recovery processes and the agent monitoring processes in accessing the table. Note`Tabular array` is simply required if in-depth monitoring is used. If the `PWord` varies by RAC example, it must as well be defined as local.

If other attributes for the Oracle resources differ for diverse RAC instances, define them locally likewise. These other attributes may include the Oracle resources attributes User, PWord, the CVMVolDg resources 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 letters:

/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 and so on, may be required. The engine_A.log contains the near recent data.