Serviceguard support for ASM on HP-UX 11i v3 onwards
This document describes how to configure Oracle ASM database with Serviceguard for high availability using the ECMT Oracle toolkit. Look at the ECMT support matrix available at http://
Note that for a database failover, each database should store its data in its own disk group. Refer to Oracle documentation for limitation imposed by ASM on the number of disk groups. The disk group members must be logical volumes managed by HP Logical Volume Manager (LVM). Initial release of
2 logical volumes are also supported as members of the ASM disk groups.
A new I/O infrastructure that enables the native
A new cluster wide DSF format is introduced in
It is the responsibility of Serviceguard to provide the necessary I/O fencing when failover is provided for a
Framework for ASM support with Serviceguard
The framework for ASM integration with Serviceguard makes use of a
•Avoid failing over ASM instance. This reduces the failover time due to ASM instance restart.
•Many database instances can share one ASM instance per node.
•Sequencing between Oracle database instance and ASM instance during startup/shutdown/failover.
•Flexibility of the database instances to fail over independently.
HP provides a set of scripts known as the Enterprise Cluster Master Toolkit (ECMT) scripts which provides for the integration of ASM with Serviceguard. The operation of the Toolkit is described below.
The start function switches to the ASM software owner user id by executing the su command. It starts the ASM instance specified by the user using the sqlplus commands. The mounting of the ASM disk groups associated with a database instance will be done before database instance startup after volume group activation during the database package startup.
The stop function executes su to the ASM software owner user id. It stops the ASM instance using sqlplus commands.
The monitor function contains a continuous loop to check if the ASM instance processes specified are healthy. If the monitor function finds any process to have died, it means that the ASM instance has either failed or been inappropriately shut down, that is, without using cmhaltpkg. The service