HP Serviceguard Enterprise Cluster Master Toolkit User Guide, June 2014

Figure 4 ASM environment when DB1 fails on node 2
Serviceguard Toolkit Internal File Structure
HP provides a set of scripts for the framework proposed for ASM integration with Serviceguard.
The ECMT Oracle scripts contain the instance specific logic to start/stop/monitor both the ASM
and the database instance. These scripts support both legacy and the modular method of packaging.
HP recommends that you use the modular method of packaging, because the legacy method is no
longer approved and will not be supported in future. For more information on creating a modular
package, see latest Managing Serviceguard manual available at http://www.hp.com/go/
hpux-serviceguard-docs—>HP Serviceguard . Serviceguard provides tools to migrate existing
legacy packages to modular packages. For more information, see whitepaper “Migrating Packages
from Legacy to Modular Style” available at http://www.hp.com/go/hpux-serviceguard-docs-> HP
Serviceguard.
Legacy packages use the package configuration file and the package control script for the ASM
or database instance on the Serviceguard. The package configuration file parameters are stored
in the Serviceguard configuration database (CDB) at cmapplyconf time, and are used by the
package manager when it acts on behalf of this package. The control script invokes the ASM or
the database instance specific functions for start/stop/monitor through the toolkit interface script
(toolkit.sh). On the instance specific side, there is a toolkit configuration file (haoracle.conf) which
is sourced by the start/stop/monitor (haoracle.sh,haoracle_sql.sh, haoracle.mon,
and halistener.mon) script files. The toolkit interface script allows the start/stop/monitor calls
to remain unaffected by changes in the instance specific scripts. Figure 5, shows the internal file
structure for legacy packages.
Supporting Oracle ASM Instance and Oracle Database with ASM 37