Enterprise Cluster Master Toolkit User Guide April 2011 (5900-1606)

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.
1. ORA_CRS_HOME: When using ECMT oracle toolkit in a coexistence environment, this attribute
must be set to Oracle CRS HOME.
2. OC_TKIT_DIR: When using ECMT Oracle in a coexistence environment, this attribute must be
set to the SGeRAC Toolkit’s Oracle Clusterware (OC) package directory.
Figure 7 describes the various package dependencies between the single-instance Oracle database
package created using ECMT and the Oracle RAC packages created using SGeRAC.
Figure 7 Packages in a coexistence environment
Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages 53