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 18 User Variables in hamysql.conf file (continued)
DescriptionFile name
This variable enables or disables maintenance mode for the MySQL
package. By default, this is set to "yes". To disable this feature
MAINTENANCE_FLAG (for example,
MAINTENANCE_FLAG="yes")
MAINTENANCE_FLAG must be set to "no". When MySQL needs
maintenance, the file <package directory>/mysql.debug
must be created. During this maintenance period, the MySQL process
monitoring is paused. Even if the MySQL instance is brought down
the package does not failover over to the adoptive node. To continue
monitoring and turn off maintenance mode, you must remove the
mysql.debugfile. You must ensure that the MySQL instance is
running properly before exiting the maintenance phase, because
monitoring of the instance resumes when it is out of the maintenance
phase.
This variable is recommended to be set to "0". This will multiply the
SERVICE_RESTART of the MySQL package service (monitor).
RETRY_TIMES=0
For example, If the package service is set to SERVICE_RESTART = 2
& RETRY_TIMES=2 then actual retries = (SERVICE_RESTART + 1) *
RETRY_TIMES.
This is the interval at which hamysql.mon monitors the process with
PID in the PID_FILE (mysqld parent process).
MONITOR_INTERVAL=5 # Seconds.
The time unit granularity is seconds. Therefore, setting MONITOR_INTERVAL=5 means the parent
process is monitored every 5 seconds.
Package Configuration File and Control Script
The following steps identify the changes needed to the Serviceguard package configuration file
and control script templates to customize them for your specific configuration. For more information,
see the "Configuring Packages and Their Services" of the Managing Serviceguard manual available
at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard manual. For detailed
information on configuring and managing a package, see the "Managing Serviceguard" manual.
The parameters in Table 20 are either in the configuration file or control script as identified in the
table, and must be manually edited for your unique environment. Table 19 (page 93), assigns
values to the package "mysql_1".
Table 19 Package Configuration File Parameters
DescriptionConfiguration file
Parameter Name [configuration
file parameters]
# Package Namemysql_1PACKAGE_NAME
# nodes that can run the packagenode1, node2NODE_NAME NODE_NAME
Script to start up the service<control script>RUN_SCRIPT
# Script to halt the service<control script>HALT_SCRIPT
# Service Name"mysql_monitor"SERVICE_NAME
Table 20 Package Control Script Parameters
DescriptionControl script
Parameter Name [control script
parameters]
# VG created for this packagevgMySQLVG
# Logical vol created in VT/dev/vgMySQL/lvol1LV
# File system for DB/MySQL_1FS
Package Configuration File and Control Script 93