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
For legacy packages, there is one user configuration script (hadb2.conf) and three functional
scripts (toolkit.sh, hadb2.sh, and hadb2.mon) which work with each other to integrate
DB2 with the Serviceguard package control scripts.
For modular packages, there is an Attribute Definition File (ADF), a Toolkit Module Script
(tkit_module.sh), and a Toolkit Configuration File Generator Script (tkit_gen.sh) that work
with the three scripts (toolkit.sh, hadb2.sh and hadb2.mon) for legacy packages to integrate DB2
with the Serviceguard Master Control Script.
Table 8 (page 79) lists these the scripts:
Table 8 Legacy Package Scripts
DescriptionScript Name
This script contains a list of pre-defined variables that you must customize for
use with a particular database instance. This is a configuration file which is
hadb2.conf (user configuration file)
read by the toolkit script, hadb2.sh. The table Table 9 (page 79) shows
variables that are contained in hadb2.conf.
This script contains a list of internally used variables and functions that support
starting and stopping of a DB2 database instance. This script is called by
toolkit.sh to perform the following:
Main Script (hadb2.sh)
• On package startup, it starts the DB2 instance and monitor process.
• On package halt, it stops the DB2 instance and monitor process.
This script contains a list of internally used variables and functions for
monitoring a DB2 server instance. This script iscalled by hadb2.sh . It uses a
tool called "db2gcf" to monitor the database.
Monitor Script (hadb2.mon)
This script is the interface between the Serviceguard package control script
and the DB2 toolkit.
Interface Script (toolkit.sh)
Table 9 Variables in hadb2.conf File
DescriptionVariable Name
The DB2 instance name.INSTANCE_NAME
You can use the INSTANCE_USER variable to start, stop, and monitor the
DB2 instance. The value for INSTANCE_USER must be the Instance owner or
INSTANCE_USER
any user with root privilege. The default value for the INSTANCE_USER is
${DB2_INSTANCE_NAME}. In HP-UX, the DB2 Instance name and Instance
owner name is the same. To manage the instance by a user other than Instance
owner, provide the user name as the INSTANCE_USER value. For example:
INSTANCE_USER user1.
The list of the logical database partitions that participate in a DB2 instance
and are intended to run on single server. Physical partitions must be packaged
separately.
PARTITION_NUMBER
This is the list of critical processes of a DB2 instance.MONITOR_PROCESSES
NOTE: These processes must not be running after DB2 is shutdown. If the
processes are still running they are killed by sending a SIGKILL.
This variable will enables or disables maintenance mode for DB2 package.
By default, this is set to "yes". To disable this feature MAINTENANCE_FLAG
MAINTENANCE_FLAG
must be set to "no". When DB2 Database needs maintenance, a file
"<package directory>/db2.debug" must be created. During this maintenance
period process monitoring for DB2 database instance is paused. Even if DB2
instance is brought down, the package does not failover to the standby node.
To continue monitoring and come out of the maintenance mode, you must
remove the file "db2.debug" from the package configuration directory. You
must ensure that db2 instance is properly running after the maintenance phase.
Setting up the Toolkit 79