HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

NOTE:
• If the package fails during maintenance (example, the node crashes), the package does
not automatically fail over to an adoptive node. You must start the package up on an
adoptive node. For more information, see the latest Managing Serviceguard manual
available at http://www.hp.com/go/hpux-serviceguard-docs—>HP Serviceguard .
If the Oracle database package is dependent on the SGeRAC OC MNP, the Oracle
database package automatically goes to toolkit maintenance mode when the SGeRAC
OC MNP is put into toolkit maintenance mode. To put the SGeRAC OC MNP into toolkit
maintenance mode, its MAINTENANCE_FLAG attribute must be set to 'yes' and a file
'oc.debug' must exist in its package directory. For more information on how to put the
SGeRAC OC MNP in toolkit maintenance mode, See the SGeRAC toolkit README filen.
If the MAINTENANCE_FLAG attribute of the SGeRAC OC MNP is set to 'yes', this
parameter must also be set to 'yes'.
• HP suggests you to have different toolkit directories for each package. If two or more
packages share the same toolkit directory and if one package enters the maintenance
mode, it will affect the other package too.
Configuring and packaging Oracle single-instance database to co-exist
with SGeRAC packages
This section describes the way in which ECMT Oracle toolkit package must be configured for
single-instance Oracle databases to work in a Serviceguard cluster, along with RAC database
packages configured using SGeRAC Toolkit.
NOTE: The environment in which both ECMT Oracle packages and SGeRAC packages are
running together is called ‘coexistence environment’ in this document.
Configuring Oracle single-instance database that uses ASM in a Coexistence
Environment
The single-instance Oracle databases using ASM are supported in SGeRAC/Serviceguard clusters
only when ASM Disk Groups are configured using LVM Logical Volumes. In a coexistence
environment, the following additional conditions also apply:
1. The Oracle Clusterware must be configured in a MNP package using SGeRAC Toolkit. See
the Using Serviceguard Extension for RAC" User Guide (published March 2011 or later)
available at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard Extension
for RAC/opt/cmcluster/SGeRAC/toolkit/README file for configuring Oracle Clusterware
(SGeRAC OC MNP package) as a package.
2. The ASM Multi-node package (MNP) must not be created using the ECMT toolkit. The ASM
instances are managed by the SGeRAC Oracle Clusterware package.
3. The single-instance databases must be disabled for automatic startup by Oracle Cluster Ready
Service (CRS).
The ECMT failover package for single-instance Oracle database must have the following additional
configuration:
1. The ASM Disk Groups and underlying LVM volume groups used by the single-instance Oracle
database must be configured as part of the database’s ECMT failover package.
2. A SAME_NODE UP package dependency on SGeRAC Oracle Clusterware package must be
configured in the ECMT failover package for the Oracle single-instance database.
3. The attributes: ORA_CRS_HOME and OC_TKIT_DIR must be specified with appropriate values
as specified in section “Attributes newly added to ECMT”.
Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages 57