HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)
Table Of Contents
- HP Serviceguard Enterprise Cluster Master Toolkit User Guide
- Contents
- 1 Introduction
- 2 Using the Oracle Toolkit in an HP Serviceguard Cluster
- Overview
- Supported Versions
- Support for Oracle Database Without ASM
- Supporting Oracle ASM Instance and Oracle Database with ASM
- What is Automatic Storage Management (ASM)?
- Why ASM over LVM?
- Configuring LVM Volume Groups for ASM Disk Groups
- Sample command sequence for configuring LVM Volume Groups
- Serviceguard support for ASM on HP-UX 11i v3 onwards
- Framework for ASM support with Serviceguard
- Installing, Configuring, and Troubleshooting
- Setting up DB instance and ASM instance
- Setting up the Toolkit
- ASM Package Configuration Example
- Modifying a Legacy Database Package Using an Older Version of Oracle ECMT Scripts to use the Scripts Provided for ASM Support
- Adding the Package to the Cluster
- Node-specific Configuration
- Error Handling
- Network Configuration
- Database Maintenance
- Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages
- Configuring Oracle single-instance database that uses ASM in a Coexistence Environment
- Attributes newly added to ECMT Oracle toolkit
- Configuring a modular failover package for an Oracle database using ASM in a coexistence environment
- Configuring a legacy failover package for an Oracle database using ASM in a Coexistence Environment
- ECMT Oracle Toolkit Maintenance Mode
- Supporting EBS database Tier
- Oracle ASM Support for EBS DB Tier
- 3 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX
- Overview
- Sybase Information
- Setting up the Application
- Setting up the Toolkit
- Sybase Package Configuration Example
- Creating the Serviceguard package using Modular method
- Adding the Package to the Cluster
- Node-specific Configuration
- Error-Handling
- Network configuration
- Database Maintenance
- Cluster Verification for Sybase ASE Toolkit
- 4 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX
- 5 Using MySQL Toolkit in a HP Serviceguard Cluster
- MySQL Package Configuration Overview
- Setting Up the Database Server Application
- Setting up MySQL with the Toolkit
- Package Configuration File and Control Script
- Creating Serviceguard Package Using Modular Method
- Applying the Configuration and Running the Package
- Database Maintenance
- Guidelines to Start Using MySQL Toolkit
- 6 Using an Apache Toolkit in a HP Serviceguard Cluster
- 7 Using Tomcat Toolkit in a HP Serviceguard Cluster
- Tomcat Package Configuration Overview
- Multiple Tomcat Instances Configuration
- Configuring the Tomcat Server with Serviceguard
- Setting up the Package
- Creating Serviceguard Package Using Modular Method
- Setting up the Toolkit
- Error Handling
- Tomcat Server Maintenance
- Configuring Apache Web Server with Tomcat in a Single Package
- 8 Using SAMBA Toolkit in a Serviceguard Cluster
- 9 Using HP Serviceguard Toolkit for EnterpriseDB PPAS in an HP Serviceguard Cluster
- 10 Support and Other resources
- 11 Acronyms and Abbreviations
- Index

Table 6 Variables or Parameters in haoracle.conf file (continued)
DescriptionParameter Name
The home directory where ASM is installed. This parameter must be set for both
the ASM and the ASM database instance packages.
ASM_HOME
The user name of the Oracle ASM administrator. This parameter must be set
for both ASM instance and ASM database instance packages.
ASM_USER
The ASM session name. This uniquely identifies an ASM instance. If the database
instance package depends on the ASM MNP package, this parameter needs
ASM_SID
to be set for both the ASM and the database instance packages. This parameter
need not be set in case the database instance package depends on the SGeRAC
clusterware package (OC MNP). This parameter is set to "+ASM" by default.
Oracle database /ASM parameter file. If not specified, Oracle picks this up
from the Oracle configuration directory $ORACLE_HOME/dbs or
$ASM_HOME/dbs depending on the INSTANCE_TYPE.
PFILE
This parameter, when configured, overrides the default file or location. If both
PFILE and SPFILE are present and this parameter is not specified, the Oracle
SPFILE
scripts uses PFILE as the parameter file. To make use of SPFILE in the scripts, do
not configure this parameter and remove the default PFILE from its default
location. This parameter must be set for both the ASM and the database instance
packages.
NOTE: For Oracle 11gR2, by default, the spfile of the ASM instance is stored
on the ASM diskgroup. This is true only for the ASM instance and not for the
database instance that uses the ASM diskgroup. For an ASM instance, the ECM
Toolkit cannot verify the existence of the spfile on the ASM diskgroup. So, it is
mandatory that a pfile is created from the spfile on the local disk, at a location
that ECMT can access. For 11gR2 ASM instance, the value of the PFILE attribute
must point to the pfile that is created on the local disk.
Set to "yes" if you want the scripts to start and stop the Oracle Listener. This
parameter must be set only in the database instance package.
LISTENER
The name of the listener process. This parameter must be set only in the database
instance package.
LISTENER_NAME
The password of the listener process. This parameter must be set only in the
database instance package.
LISTENER_PASS
The names of all processes that should be executing. This parameter must be
set for the ASM and the database instance packages. The description of this
MONITOR_PROCESSES
attribute in the package configuration file has a sample of processes that must
be monitored for ASM and database instances.
This variable will enables or disables toolkit maintenance mode for the Oracle
database package and ASM MNP. By default, this is set to yes. To disable
MAINTENANCE_FLAG
this feature, MAINTENANCE_FLAG must be set to no. When Oracle Database
or ASM must be maintained, a file <package directory >/oracle.debug
must be created. During this maintenance period, the process monitoring for
the Database or ASM instance is paused. Even if the instance is brought down,
its package is not failed over to the standby node.
To continue monitoring and to exit from the maintenance mode, you must
remove the oracle.debug file. You must ensure that the instance is properly
running after the maintenance phase is complete. This parameter can be set in
the ASM and database instance package.
42 Using the Oracle Toolkit in an HP Serviceguard Cluster