Using the Oracle Toolkit in a HP Serviceguard Cluster README Revision: B.06.00, August 2010

Serviceguard, please refer to the whitepaper "Support for Oracle
10gR2 and
11gR1 ASM with Serviceguard on HP-UX 11iv2 and 11iv3" available at:
www.hp.com/go/hpux-serviceguard-docs -> HP Enterprise Cluster
Master Toolkit
The Oracle toolkit uses Multi-Node Package (MNP) and the package
dependency
feature to integrate Oracle ASM with HP Serviceguard. An MNP is used to
encapsulate the per-node ASM instances with one or more Oracle single
instance
failover packages that are dependent on this MNP. This configuration
enables
database instance to start up in the right order in relation to the ASM
instance,
and in the event of a failover, to relocate to a node where an ASM
instance is
available.
The Oracle toolkit scripts for ASM support with Serviceguard consists
of a set
of shell scripts that are used to start, stop and monitor an Oracle ASM
and
database instance and the configured listeners. To use these scripts,
the scripts must be integrated into the Serviceguard package control
script in
case of legacy packages. In the case of modular packages, the scripts
must be
integrated with the Serviceguard master control script. Subsequent
sections
provide guidelines for integrating these scripts with the Serviceguard
package
control script and the master control script.
i. Setting Up the Application
This section describes the sequence of steps to be followed to set up
an
ASM instance or a database instance using ASM storage.
- Configuring ASM in a Serviceguard environment and creating the ASM
instance
1. Configure the raw logical volumes to be used in the ASM disk
groups as
mentioned in the whitepaper "Support for Oracle 10gR2 and 11gR1 ASM
with
Serviceguard on HP-UX 11iv2 and 11iv3" present at
http://www.hp.com/go/hpux-serviceguard-docs -> HP Enterprise Cluster
Master Toolkit
Assign the right set of ownership and permissions to the raw
logical volumes (oracle:dba and 0660 respectively).