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
/dev/vg0_payroll/lvol1 (the logical volume)
/dev/vg0_payroll/lvol1 (the filesystem) mounted at /mnt/payroll
2. Test the set up to ensure that DB2 can be properly brought up. Tert st DB2 to ensure that it
can be properly started by executing the script toolkit.sh.
For example:
cd /tmp/db2
cp /opt/cmcluster/toolkit/db2/* .
Edit the DB2 toolkit configuration file hadb2.conf
./toolkit.sh start
After waiting for a few minutes, check for the several existence of DB2 processes which are
identified by "db2" , ps -ef | grep db2. Bring the database down, unmount, and deactivate
the volume group.
./toolkit.sh stop
umount /mnt/payroll
vgchange -a n /dev/vg0_payroll
Repeat this step on all other clustered nodes that must be configured to run the package and
ensure that DB2 can be brought up and down successfully.
The following section describes the methods for creating Serviceguard package using the
modular and legacy method. For more information on creating Serviceguard package using
modular method, see white paper Modular package support in Serviceguard for Linux and
ECM Toolkits available at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard
Enterprise Cluster Master Toolkit.
Creating Serviceguard package using Modular method
Create the Serviceguard package using Modular method.
To create Serviceguard package using Modular method, follow the below steps:
1. Create a directory for the package:
#mkdir /etc/cmcluster/pkg/db2_pkg/
2. Copy the toolkit template and script files from db2 directory:
#cd /etc/cmcluster/pkg/db2_pkg/
#cp /opt/cmcluster/toolkit/db2/* ./
3. Create a configuration file (pkg.conf).
#cmmakepkg -m ecmt/db2/db2 pkg.conf
4. Edit the package configuration file.
NOTE: DB2 toolkit configuration parameters in the package configuration file are prefixed
by ecmt/db2/db2 when used in Serviceguard A.11.19.00 or later. For example,
/etc/cmcluster/pkg/db2_pkg/pkg.conf
The configuration file must be edited as indicated by the comments in that file. The package
name must be unique within the cluster. For clarity, use the name of the database instance to
name the package. For example,
PACKAGE_NAME db2_payroll
List the names of the clustered nodes that must be configured to run the package, using the
NODE_NAME parameter.
NODE_NAME node1
NODE_NAME node2
Set the script_log_file variable. For example,
script_log_file /etc/cmcluster/pkg/<pkg_dir>/log
DB2 Package configuration example 81