HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

NOTE: If the package fails during maintenance (example, the node crashes), the package
will not automatically fail over to an adoptive node. It is the responsibility of the user to start
the package up on an adoptive node. See the manual Managing ServiceGuard manual
available at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard for more
details.
If the Oracle database package is dependent on the SGeRAC OC MNP, then the Oracle
database package will automatically go 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. See the SGeRAC toolkit README file for information details
on how to put the SGeRAC OC MNP in toolkit maintenance mode. If the MAINTENANCE_FLAG
attribute of the SGeRAC OC MNP is set to 'yes', then this parameter must also be set to 'yes'.
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 will be referred to as ‘coexistence environment’ in this document.
Configuring Oracle single-instance database that uses ASM in a Coexistence
Environment
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 will be managed by the SGeRAC Oracle Clusterware package.
3. 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”.
Attributes newly added to ECMT Oracle toolkit
The following attributes are added to ECMT oracle toolkit. These attributes are required to be
populated only for coexistence in a SGeRAC cluster. When there are no SGeRAC packages
configured in the same cluster, these attributes must be left empty.
Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages 53