Serviceguard Extension for RAC Version A.11.18 Release Notes, 5th Edition, October 2008

...
GMS_USER[n-1]=<oraclen>
4. Restart the Serviceguard cluster.
5. Restart Oracle Clusterware (for Oracle 10g and 11g) and Oracle RAC database instance on
all nodes.
Use the following steps to disable the GMS authorization:
Disable GMS authorization
1. If Oracle RAC database instance and Oracle Clusterware (for Oracle 10g and 11g) are running
shut them down on all nodes.
2. Halt the Serviceguard cluster.
3. Edit /etc/opt/nmapi/nmutils.conf and comment the GMS_USER[] settings on all
nodes.
4. Restart the Serviceguard cluster.
5. Restart Oracle Clusterware (for Oracle 10g and 11g) and Oracle RAC database instance on
all nodes.
Support for 8192 Oracle Server Processes for Oracle 9i, 10gR2 and 11gR1 RAC
The maximum number of Oracle server processes cmgmsd can handle is 8192. When there are
more than 8192 server processes connected to cmgmsd, it will start to reject new requests. Oracle
foreground server processes are needed to handle the requests of the Data Base (DB) client
connected to the DB instance.
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.
Serviceguard Extension for RAC does not support Mixed Clusters
For SGeRAC, the nodes in the cluster must be on the same architecture. SGeRAC does not support
clusters containing mixed architectural nodes, which consist of HP 9000 and HP Integrity servers,
or different operating system releases.
About Device Special Files (DSFs)
HP-UX releases up to and including 11i v2 use a naming convention for device files that encodes
their hardware path. For example, a device file named /dev/dsk/c3t15d0 would indicate
SCSI controller instance 3, SCSI target 15, and SCSI LUN 0. HP-UX 11i v3 introduces a new
nomenclature for device files, known as agile addressing (sometimes also called persistent LUN
binding). Under the agile 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
pre-11i v3 device files, which as of 11i v3 are referred to as legacy device files. Device files using
the new nomenclature are called persistent device files, When you upgrade to HP-UX 11i v3, a
set of new, persistent device files is created, but the existing, legacy device files are left intact
and by default will continue to be used by HP-UX and Serviceguard.
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 (see the white paper The Next Generation
Mass Storage Stack under Network and Systems Management -> Storage Area Management at
docs.hp.com).
14 Serviceguard Extension for RAC Version A.11.18 Release Notes