Using Serviceguard Extension for RAC, 6th Edition, April 2008

addressing convention, the hardware path name is no longer encoded in a storage
device’s name; instead, each device file name reflects a unique instance number, for
example /dev/[r]disk/disk3, that does not need to change when the hardware
path does. Agile addressing is the default on new 11i v3 installations, but the I/O
subsystem still recognizes the pre-11i v3 nomenclature. This means that you are not
required to migrate to agile addressing when you upgrade to 11i v3, though you should
seriously consider its advantages. It is possible, though not a best practice, to have
legacy DSFs on some nodes and agile addressing on others; this allows you to migrate
the names on different nodes at different times, if necessary.
Operating System Parameters
The maximum number of Oracle server processes cmgmsd can handle is 8192. When
there are more than 8192 server processes connected to cmgmsd, then cmgmsd will start
to reject new requests.
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:
Operating System Parameters 99