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
NOTE: In a Serviceguard cluster environment, the fault monitor facility provided by DB2
must be turned off. Fault monitor facility is a sequence of processes that work together to
ensure that DB2 instance is running. Fault monitor facility is specifically designed for
non-clustered environments and has the flexibility to be turned off if the DB2 instance is running
in a cluster environment. In Serviceguard environment, DB2 instance start/stop is controlled
by Serviceguard and hence the fault monitor facility must be turned off.
For more information on this, see the IBM DB2 documentation available at https://
publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp and https://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp .
You must repeat the steps 1 to 12 on all nodes in the cluster. Steps 5-12 mentioned above
are applicable for multi-partition database setup. Single partition users need not defer the
instance creation while installing as mentioned in step 4. After the installation is complete,
you can continue from step 11 onwards.
Multiple Instance Configurations
If multiple instances run in the same cluster, repeat the steps "Setting up the application" for each
instance. For example, if a second instance (employee) must be included in the configuration, you
must create a second volume group (for example, /dev/vg_employee ), logical volume, and
filesystem with mount point (/mnt/employee ) for the second instance. With this configuration,
it is possible to run several DB2 instances on one node, facilitating failover/failback of DB2
packages between nodes in the cluster.
Set up additional database logical volumes
The database resides on several volume groups and logical volumes, which must be shared among
the nodes that are able to run the DB2 instances. You can use a naming convention for the VGs
that include the instance name to associate a VG with a unique instance.
NOTE: To create logical volumes, seeStep1 Step 1 in “Setting up the application”
For example:
Raw disk access for DB2 data:
/dev/vg01_payroll/rlvol1 #Raw logical volume DB2 data
/dev/vg02_payroll/rlvol1 #Raw logical volume DB2 data
/dev/vg03_payroll/rlvol2 #Raw logical volume DB2 data
or for use with Asynchronous disk access and file systems:
/dev/vg01_payroll/lvol1 #Logical volume DB2 data
/dev/vg02_payroll/lvol1 #Logical volume DB2 data
/dev/vg03_payroll/lvol2 #Logical volume DB2 data
Setting up the Toolkit
Toolkit Overview
After the toolkit installation is complete, three scripts and the README file will be present in the
/opt/cmcluster/toolkit/db2/ directory. Two more scripts and one Attribute Definition File
are present which will be used only by modular packages. These scripts are in the /etc/
cmcluster/scripts/ecmt/db2/ directory. The Attribute Definition file for modular packages
are predefined and include the identity of the database instance as per the name set in the /etc/
cmcluster/modules/ecmt/db2/ directory.
78 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX