HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

1. The attribute PARENT_ENVIRONMENT in the package configuration file must be set to “yes”.
2. The required environment variables must be defined in the file customer.conf and placed
in the package directory (TKIT_DIR).
WARNING! HP recommends you not to override the Oracle toolkit attributes defined in the
package configuration through this file.
Cluster verification for ECMT - Oracle Toolkit
Cluster verification is a proactive mechanism to identify cluster inconsistencies that adversely affects
toolkit package failover to a node. It is a check for Serviceguard, Toolkit, and Oracle database
versions on all the package nodes of the cluster. Cluster verification is supported in Serviceguard
A.11.20.00 and ECMT B.06.00 Patch A or later. It does not fail the cmcheckconf command,
but logs appropriate warning messages are logged. In future, you can add new checks in an
incremental fashion, transparent to Serviceguard.
Example:
Consider a two-node cluster, both nodes having Serviceguard A.11.20 and ECMT B.06.00 but
different Oracle database versions. Use cmcheckconf command to check package configuration.
For example: node1# cmcheckconf -P pkg.conf
On node1, validation of the package Oracle_pkg, succeeded with:
The toolkit configuration file will be backed up and a new file will be created in tkit_dir when the package
configuration is applied.
On node2, validation of package Oracle_pkg succeeded with:
The toolkit configuration file in the configuration directory are backed up and a new file is created in tkit_dir
when the package configuration is applied.
WARNING: Oracle database version on all package nodes does not match.
Check syslog for more details.
cmcheckconf: Verification completed. No errors found.
Use the cmapplyconf command to apply the configuration.
Oracle package configuration example
Package Setup and Configuration
Consider that Oracle is already installed in its default home directory (for example, /home/oracle),
perform the following steps to make necessary directories shareable by all clustered nodes:
If you are using LVM or VxVM
For more information on creating a logical volume infrastructure on a shared disk, see section
Building an HA Cluster Configuration in the latest Managing Serviceguard manual available at
http://www.hp.com/go/hpux-serviceguard-docs—>HP Serviceguard . The disk must be available
to all clustered nodes that will be configured to run this database instance. Create a file system to
hold the necessary configuration information and symbolic links to the Oracle executables. This
file system will be used as ORACLE_HOME in the package control scripts. Since the volume group
and file system have to be uniquely named within the cluster, use the name of the database instance
($SID_NAME) in the name. Consider that the name of the database is 'ORACLE_TEST0', follow
the instructions in the section Building an HA Cluster Configuration in the latest Managing
Serviceguard manual available at http://www.hp.com/go/hpux-serviceguard-docs—>HP
Serviceguard to create the following:
LVM
----
/dev/vg0_ORACLE_TEST0 (the volume group)
/dev/vg0_ORACLE_TEST0/lvol1 (the logical volume)
/dev/vg0_ORACLE_TEST0/lvol1 (the filesystem)
mounted at /ORACLE_TEST0
VxVM
-----
/dev/vx/dsk/DG0_ORACLE_TEST0 (the disk group)
Support for Oracle Database Without ASM 21