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

DescriptionAttributes
down on the local node, the RAC MNP on that node is not halted.To continue monitoring
and come back from the maintenance mode on one node, you must remove the "rac.debug"
file on that node. You must ensure that the Oracle RAC instance is properly running after
the maintenance phase.
This parameter contains a directory path where the Oracle Clusterware toolkit configuration
file (oc.conf) is generated. The toolkit maintenance mode flag file (oc.debug) must
OC_TKIT_DIR
be created in this directory to put the package in toolkit maintenance mode.During a
modular package configuration, this parameter is automatically set by cmapplyconf
command. You can also specify a desired path, if you do not want the default settings.If
the MAINTENANCE_FLAG is set to no, OC_TKIT_DIR is not required, and the RAC MNP
will not check the OC MNP's maintenance status.
By default, this parameter is automatically set by cmapplyconf command during a modular
package configuration. If you specify a path, then the same path is used. When the
MAINTENANCE_FLAG is yes, it is used to check the ASMDG MNP maintenance status.
NOTE: This parameter must be set only if the new ASM DG model is used.
This parameter contains a directory path where the ASMDG toolkit configuration file
(asm_dg.debug) is generated. This is also a directory in which the toolkit maintenance
mode flag file (asm_dg.debug) must be created to put this package in toolkit maintenance
mode.
ASM_TKIT_DIR
By default, this parameter is commented. It means that Oracle RAC Database services are
not started or stopped as part of RAC-MNP. You must manually start or stop the database
DB_SERVICE
services. Uncomment and specify the Oracle RAC Database service names which needs
to be started or stopped as part of RAC-MNP. If the keyword, all is used, RAC-MNP starts
or stops all the Database services configured.
HP recommends that you specify the keyword all as a first entry in an array. After the
keyword all is mentioned, the RAC MNP ignores other services which might be specified
in the DB_SERVICE array.
If RAC-MNP is deployed through Serviceguard Manager Package Easy Deployment,
DB_SERVICE will have the keyword “all” by default.
To start all services configured in the RAC database managed by this package, set this
attribute to all for example:
DB_SERVICE[0] = all
To start and stop Services dbsrv1, dbsrv2, and dbsrv3 through the RAC-MNP, specify the
service names using multiple instances of this attribute for example:
DB_SERVICE[0] = dbsrv1
DB_SERVICE[1] = dbsrv2
DB_SERVICE[2] = dbsrv3
SGeRAC Toolkit Supported Configurations
This version of Toolkit supports the following configurations. The maximum number of nodes
supported in SGeRAC Toolkit depends on the number of nodes supported by SGeRAC with each
storage management configuration.
Refer to "Number of nodes supported in SGeRAC for SLVM, CVM and CFS Matrix" posted on
http://www.hp.com/go/hpux-serviceguard-docs -> Serviceguard Extension for RAC.
HP-UX versionStorage ManagementToolkit Multi-Node package
11i v3SLVM rawOracle Clusterware
11i v3ASM over HP-UX raw disks (For
11gR2 or later)
Oracle Clusterware
11i v3ASM over SLVM logical volumes (For
11gR2 or later)
Oracle Clusterware
Using Serviceguard Packages to Synchronize with Oracle 10gR2/11gR1/11gR2 RAC 75