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
The toolkit monitor script (database instances) that continuously monitors DB2 partitions will
now stop monitoring these partitions.
The message, "DB2 toolkit pausing, monitoring, and entering maintenance mode", appears
in the Serviceguard Package Control script log for legacy packages and package configuration
log file in case of modular style of packaging.
• If required, stop the DB2 database instance:
$ cd /etc/cmcluster/pkg/db2_pkg/
$ $PWD/toolkit.sh stop
• Perform maintenance actions (For example, changing the configuration parameters in the
parameter file of the DB2 instance. If this file is changed, you must distribute the new file to
all cluster nodes).
• Start the DB2 database instance again if you have stopped it:
$ cd /etc/cmcluster/pkg/db2_pkg/
$ $PWD/toolkit.sh start
• To continue monitoring, enable monitoring scripts by removing db2.debug file:
$ rm -f /etc/cmcluster/pkg/db2_pkg/db2.debug
The message "Starting DB2 toolkit monitoring again after maintenance" appears in the
Serviceguard Package Control script log.
• Enable the package failover:
$ cmmodpkg -e db2_payroll
NOTE:
• If the package fails during maintenance (for example, the node crashes) the package does
not automatically fail over to an adoptive node. You must start the package up on an adoptive
node. For more information, see the latest Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard .
This feature is enabled only when the configuration variable MAINTENANCE_FLAG is set to
"yes" in the DB2 toolkit configuration file.
• HP suggests you to have different toolkit directories for each package. If two or more packages
share the same toolkit directory and if one package enters the maintenance mode, it will affect
the other package too.
Cluster Verification for DB2 Database Toolkit
Cluster verification is a proactive mechanism to identify cluster inconsistencies that adversely affects
toolkit package failover to a node. This mechanism checks for Serviceguard, ECMT, DB2 versions,
and supported Database Partitioning feature on all the package nodes of the cluster. If there are
any inconsistencies, it does not fail the cmcheckconf command, but logs appropriate warning
messages.
Example:
Consider a two-node cluster, where both nodes have Serviceguard A.11.20, ECMT B.07.00.01,
or later but different DB2 versions.
To check package configuration, run the cmcheckconf command.For example: node1#
cmcheckconf -P pkg.conf
On node1, validation of the package DB2_pkg, succeeded with:
The toolkit configuration file will be backed up and a new file will be created in tkit_dir when the package
configuration is applied.
On node2, validation of package DB2_pkg succeeded with:
The toolkit configuration file will be backed up and a new file will be created in tkit_dir when the package
configuration is applied.
86 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX