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
7. Migrate the older legacy package to a modular package containing Serviceguard parameters.
# cmmigratepkg -p <legacy_pkg_name> -s -o <modular_pkg_name>
For more information, see the Whitepaper Migrating Packages from Legacy to Modular
Style,October 2007 and also the Whitepaper on modular package support in Serviceguard
at http://www.hp.com/go/hpux-serviceguard-docs -> HP Enterprise Cluster Master Toolkit
8. To add the values to this modular package configuration file, from the older toolkit configuration
file, issue the following command:
# cmmakepkg -i modular.ascii -m ecmt/oracle/oracle -t <older toolkit configuration file>
modular1.ascii
9. Now, "modular1.ascii" has values for certain attributes which were present in the older toolkit
configuration file. Parameters like ORACLE_HOME, ORACLE_ADMIN, SID_NAME, PFILE,
LISTENER, LISTENER_NAME, LISTENER_PASS, MONITOR_PROCESSES,
MAINTENANCE_FLAG, MONITOR_INTERVAL , and TIME_OUT will have values from the
old toolkit configuration file. If required, these values can be edited for the new environment.
Edit the value for TKIT_DIR (where the new toolkit configuration file should be generated or
where the toolkit scripts are copied to in case of a configuration directory mode of operation).
Retain the INSTANCE_TYPE to the default value "database". Edit the parameters ASM,
ASM_DISKGROUP, ASM_VOLUME_GROUP, ASM_HOME, ASM_USER, ASM_SID,
KILL_ASM_FOREGROUNDS, CLEANUP_BEFORE_STARTUP, and USER_SHUTDOWN_MODE
as mentioned for the database package.
10. Apply the new modular package configuration using cmapplyconf.
11. Start the database package.
Adding the Package to the Cluster
After the setup is complete, add the package to the Serviceguard cluster and start it.
$ cmapplyconf -P ORACLE_TEST0
$ cmmodpkg -e -n <node1> -n <node2> ORACLE_TEST0
$ cmmodpkg -e ORACLE_TEST0
For more information on managing packages, see the latest Managing Serviceguard manual
available at http://www.hp.com/go/hpux-serviceguard-docs—>HP Serviceguard .
Node-specific Configuration
On many clusters, the standby nodes might be lower end systems than the primary node. An SMP
machine might be backed up by a uniprocessor, or a machine with a large main memory may be
backed up by a node with less memory.
According to Oracle, you must make sure that any packaged instance can run on any specified
node in the corresponding package configuration. The Oracle shell script handles this situation in
the following way:
If node-specific tuning is required, set up a node-specific 'init.ora' file for each node in
${ORACLE_HOME}/dbs. This file should be named 'init${SID_NAME}.ora', and there should be
one such file for each host.
For Example:
/ORACLE_TEST0/dbs/initORACLE_TEST0.ora.host1
/ORACLE_TEST0/dbs/initORACLE_TEST0.ora.host2
When the Oracle shell script runs the Oracle commands, the Oracle shell script also checks the
existence of such a file before starting the Oracle database. If no host specific init file exists, a
'global' init${SID_NAME}.ora file is assumed.
54 Using the Oracle Toolkit in an HP Serviceguard Cluster