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: This setup is not supported if Oracle 10g Release 1 is configured with LVM
or VxVM. If Oracle 10g Release 1 is configured with LVM or VxVM, local
configuration is recommended. The above configuration is supported in Oracle 10g
Release 2 and Oracle 11g, only if Oracle's Automatic Storage Management (ASM)
is not configured on that node.
◦ For CFS:
In this setup, you can setup Oracle as an optional database on a CFS mounted file
system (/ORACLE_TEST0, in our example) with all Oracle binaries and configuration
files in a CFS mounted file system.
NOTE: You must install Oracle license on every node that might potentially run
Oracle in the cluster.
• Set up additional database logical volumes, with LVM
A database can reside on the same volume group or logical volume as
$ORACLE_HOME/dbs, but more commonly, the database resides on several volume
groups and logical volumes that must be shared among the nodes that are able to run
the Oracle instances. A naming convention for the volume groups that includes the instance
name (${SID_NAME}) can be used to associate a volume groups with a unique instance.
For example:
Raw disk access for Oracle data:
/dev/vg01_ORACLE_TEST0/rlvol1 # Raw logical volume Oracle data
/dev/vg02_ORACLE_TEST0/rlvol1 # Raw logical volume Oracle data
/dev/vg02_ORACLE_TEST0/rlvol2 # Raw logical volume Oracle data
or, for use with Asynchronous disk access and file systems:
/dev/vg01_ORACLE_TEST0/lvol1 # Logical volume Oracle data
/dev/vg02_ORACLE_TEST0/lvol1 # Logical volume Oracle data
/dev/vg02_ORACLE_TEST0/lvol2 # Logical volume Oracle data
See the Oracle documentation to determine the appropriate format for your environment.
All data belonging to the database must reside on shared logical volumes (raw or file
system), you must share and allocate space to the following data:
◦ Oracle tablespaces
◦ Oracle rollback segments
◦ Oracle logfiles
After you define the shared volume groups/logical volumes/file systems for
these entities, see the Oracle documentation for creating the database.
NOTE: If you are using VxVM, create appropriate disk groups.
If you are using CFS mounted file systems, the ${ORACLE_HOME}/dbs and database
can reside in the same CFS file system. Also, have multiple Oracle databases
corresponding to multiple Oracle packages can reside in the same CFS file system.
However, HP recommends that you have different CFS file systems for different Oracle
packages.
Support for Oracle Database Without ASM 13