Using Serviceguard Extension for RAC, 9th Edition, September 2010

NOTE: Starting with Oracle 10g and later, Oracle Clusterware processes register with cmgmsd
while Oracle server processes register with Oracle Clusterware. The maximum number of Oracle
server processes supported is determined by Oracle Clusterware. The maximum number of
processes registered by Oracle Clusterware should not exceed the maximum supported by
cmgmsd.
Oracle foreground server processes are needed to handle the requests of the DB client connected
to the DB instance.
Each foreground server process can either be a “dedicated” or a “shared” server process. In the
case of a dedicated process, there is a one-to-one correspondence between the DB client and the
foreground server process it invokes. The shared server processes can handle multiple DB clients.
In the case where a DB instance is configured to support a large number of DB clients, it is
necessary to adjust the maxfiles parameter. This is to make sure there are enough file descriptors
to support the necessary number of Oracle foreground and background server processes.
Creating a Storage Infrastructure with LVM
In addition to configuring the cluster, you create the appropriate logical volume infrastructure
to provide access to data from different nodes. This is done with Logical Volume Manager (LVM),
Veritas Cluster Volume Manager (CVM), or Veritas Volume Manager (VxVM). LVM and VxVM
configuration are done before cluster configuration, and CVM configuration is done after cluster
configuration.
This section describes how to create LVM volume groups for use with Oracle data. Before
configuring the cluster, you create the appropriate logical volume infrastructure to provide access
to data from different nodes. This is done with Logical Volume Manager. Separate procedures
are given for the following:
• Building Volume Groups for RAC on Mirrored Disks
• Building Mirrored Logical Volumes for RAC with LVM Commands
• Creating RAC Volume Groups on Disk Arrays
• Creating Logical Volumes for RAC on Disk Arrays
The Event Monitoring Service HA Disk Monitor provides the capability to monitor the health
of LVM disks. If you intend to use this monitor for your mirrored disks, you should configure
them in physical volume groups. For more information, refer to the manual Using HA Monitors.
Building Volume Groups for RAC on Mirrored Disks
The procedure described in this section uses physical volume groups for the mirroring of
individual disks to ensure that each logical volume is mirrored to a disk on a different I/O bus.
This kind of arrangement is known as PVG-strict mirroring. It is assumed that your disk hardware
is already configured in such a way that a disk to be used as a mirror copy is connected to each
node on a different bus than the bus that is used for the other (primary) copy.
NOTE: When using LVM the volume groups are supported with Serviceguard. The steps
shown in the following section are for configuring the volume groups in Serviceguard clusters
LVM version 1.0.
For more information on using and configuring LVM version 2.x, see the HP-UX 11i Version 3:
HP-UX System Administrator's Guide: Logical Volume Management located at:
www.hp.com/go/hpux-core-docs —> HP-UX 11iv3.
For LVM version 2 compatibility requirements, see the Serviceguard/SGeRAC/SMS/Serviceguard
Mgr Plug-in Compatibility and Feature Matrix at www.hp.com/go/hpux-serviceguard-docs
—> Serviceguard.
76 Serviceguard Configuration for Oracle 9i RAC