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: If you decide to store the configuration information on a local disk and propagate
the information to all nodes, ensure that pfile/spfile, the password file, and all control files
and data files are on shared storage. For this set up, you must set up symbolic links to the
pfile and the password file from /home/oracle/dbs as follows:
ln -s /ORACLE_TEST0/dbs/initORACLE_TEST0.ora \
${ORACLE_HOME}/dbs/initORACLE_TEST0.ora
ln -s /ORACLE_TEST0/dbs/orapwORACLE_TEST0.ora \
${ORACLE_HOME}/dbs/orapwORACLE_TEST0.ora)
• Multiple Instance Configuration
If multiple instances are running in the same cluster, repeat the preceding steps for each
instance. For example, if a second instance (ORACLE_TEST1) is to be included in the
configuration, you must do the following:
◦ For LVM
Create a second volume group (for example, /dev/vg0_ORACLE_TEST1), logical
volume, and filesystem with mount point (/ORACLE_TEST1) for the second instance.
All configuration information for ORACLE_TEST1 resides in /ORACLE_TEST1/dbs.
Similar to ORACLE_TEST0, symbolic links must be created for all subdirectories (other
than /ORACLE_TEST1/dbs/), to link /ORACLE_TEST1 to /home/oracle.
◦ For VxVM
Create a second disk group (for example, /dev/vx/dsk/DG0_ORACLE_TEST1),
logical volume, and filesystem with mount point (/ORACLE_TEST1) for the second
instance. All configuration information for ORACLE_TEST1 resides in
/ORACLE_TEST1/dbs. Similar to ORACLE_TEST0, symbolic links must be created
for all subdirectories (other than /ORACLE_TEST1/dbs/), to link /ORACLE_TEST1
to /home/oracle.
◦ For CFS
Create another directory /ORACLE_TEST1. Another CFS file system is now been
mounted on /ORACLE_TEST1 by the Serviceguard CFS packages. All configuration
information for ORACLE_TEST1 resides in /ORACLE_TEST1/dbs. Similar to
ORACLE_TEST0, symbolic links must be created for all subdirectories (other than
/ORACLE_TEST1/dbs/), to link /ORACLE_TEST1 to /home/oracle.
This configuration makes it possible to run several Oracle instances on one node,
facilitating failover or failback of Oracle packages between nodes in the cluster.
• Set up for Oracle 10g/11g single-instance database:
For LVM or VxVM (supported on Oracle 10gR2 and 11g only):
For nodes that run only one database instance, install Oracle completely on the
shared volume or file system (or ORACLE_TEST0, in our example). This process
◦
simplifies the configuration because no symbolic links are required. In this case, all
Oracle binaries and configuration is migrated to the standby node on failover.
12 Using the Oracle Toolkit in an HP Serviceguard Cluster