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
1. Consider that Sybase ASE is installed in /home/sybase; create symbolic links to all
subdirectories under /home/sybase. Exclude the dbs directory (dbs contains important instance
configuration files, and the DBS directory should reside in the shared storage in
${ASE_SERVER}, for example, /SYBASE0/dbs).
2. Test the setup to ensure Sybase ASE can be properly brought up.
3. Repeat this step on all other clustered nodes that must be configured to run the package, to
ensure Sybase ASE can be brought up and down successfully.
4. Create the Serviceguard package using modular package method
5. Create a package configuration file (SYBASE0.conf) as follows:
cmmakepkg -m ecmt/sybase/sybase -p SYBASE0.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 $ASE_SERVER to name the package
"package_name <ASE_SERVER>"
The Serviceguard package configuration file (SYBASE0.conf)
The following are some examples of modifications that must be made to the Serviceguard package
configuration file, to customize your environment.
For example:
package_name SYBASE0
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
The following is an example of specifying Sybase ASE specific variables:
ecmt/sybase/sybase/TKIT_DIR /tmp/SYBASE0
ecmt/sybase/sybase/SYBASE /home/sybase
ecmt/sybase/sybase/SYBASE_ASE ASE-15_0
ecmt/sybase/sybase/SYBASE_OCS OCS-15_0
ecmt/sybase/sybase/SYBASE_ASE_ADMIN sybase
ecmt/sybase/sybase/SALOGIN sa
ecmt/sybase/sybase/PASSWD_FILE password file name with full path
NOTE: You can retain the ecmt/sybase/sybase/PASSWD_FILE variable as commented if
the password for the administrator is not set. You can use the HP-UX access control to protect
theecmt/sybase/sybase/PASSWD_FILE variable from unauthorized user access.
ecmt/sybase/sybase/ASE_SERVER SYBASE0
ecmt/sybase/sybase/ASE_RUNSCRIPT /home/sybase/ASE-15_0/install/RUN_SYBASE0
ecmt/sybase/sybase/USER_SHUTDOWN_MODE wait
The default is "wait". If you want the ASE instance to abort immediately and therefore perform an
unclean shutdown, this should be specified as "nowait".
ecmt/sybase/sybase/MONITOR_INTERVAL 5
ecmt/sybase/sybase/TIME_OUT 30
ecmt/sybase/sybase/RECOVERY_TIMEOUT 30
ecmt/sybase/sybase/MONITOR_PROCESSES dataserver
ecmt/sybase/sybase/MAINTENANCE_FLAG yes
Define the volume groups that are used by the Sybase ASE instance. File systems associated with
these volume groups are defined as follows:
Sybase Package Configuration Example 69