Using Serviceguard Extension for RAC, 10th Edition, April 2013

Using Serviceguard Packages to Synchronize with Oracle
10gR2/11gR1/11gR2 RAC
It is recommended to start and stop Oracle Cluster Software in a Serviceguard package—the
Oracle Cluster Software will start after SGeRAC is started, and will stop before SGeRAC is halted.
Serviceguard packages should also be used to synchronize storage activation and deactivation
with Oracle Cluster Software and RAC instances.
Support for the SGeRAC Toolkit
This version of SGeRAC Toolkit supports Oracle 10gR2 Release 2, 11g Release 1, and 11g Release
2 versions and revision of RAC only.
Using SGeRAC toolkit ensures the following:
• The RAC database does not run unless the Oracle CRS is running
• The CRS package does not try to come up before it is required dependency package like SG
CFS mount point and disk group packages comes up. That is SGeRAC toolkit enforces the
proper dependencies
• The storage needed for the operation of Oracle Clusterware is activated before Oracle
Clusterware processes are started.
• The storage needed for the operation of a RAC database instance is activated the RAC
database instance is started.
• On shutdown, SGeRAC Toolkit ensures that Oracle Clusterware and the RAC database instance
are halted before deactivating the storage needed by these two entities.
About SGeRAC Toolkit
Oracle 10gR2 and later database server software offers a built-in feature called Oracle Clusterware
for building highly available RAC and single instance databases in clustered configurations. Since
the release of Oracle 10gR2, HP has recommended a combined SGeRAC-Oracle Clusterware
configuration for RAC deployments on HP-UX. In the combined stack, SGeRAC provides cluster
membership information to the Oracle Clusterware and provides clustered storage to meet the
needs of Oracle Clusterware and RAC database instances. The Oracle Clusterware manages the
database and associated resources (for example, database instances, services, virtual IP addresses,
listeners, and so on), and ASM instances, if configured.
The startup and shutdown of the various components in the combined SGeRAC-Oracle Clusterware
configuration must be coordinated in the proper sequence. The storage needed for the operation
of Oracle Clusterware must be activated before the Oracle Clusterware processes are started, and
the storage needed for the operation of a RAC database instance must be activated before the
RAC database instance is started. On shutdown, the sequence is reversed. Oracle Clusterware
and the RAC database instance must be halted before deactivating the storage needed by these
two entities.
The SGeRAC Toolkit provides the mechanism to coordinate the ordering of pieces in the combined
SGeRAC/Oracle RAC stack and the dependency between the Oracle Clusterware and Oracle
RAC instances. Also, the Toolkit offers a uniform, easy-to-manage and intuitive method to coordinate
the operation across the full range of storage management options supported by SGeRAC.
The SGeRAC Toolkit leverages multi-node package (MNP) and package dependency features
supported in SG/SGeRAC A.11.17 or later. In the SGeRAC Toolkit, scripts for configuring three
MNPs - Oracle Clusterware MNP (OC MNP), RAC database instance MNP (RAC MNP), and
Oracle Automatic Storage Management (ASM) Diskgroup MNP (ASMDG MNP) are provided.
The "OC MNP" allows SGeRAC to start/stop and monitor Oracle Clusterware processes. The
"RAC MNP" allows SGeRAC to start/stop and monitor processes of a RAC database instance.
The "ASMDG MNP" allows mounting/unmounting and monitoring of the ASM Disk groups.
68 Serviceguard Configuration for Oracle 10gR2, 11gR1, or 11gR2 RAC