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
Table 2 Legacy Package Scripts (continued)
DescriptionScript Name
This script is used to send an email to the email address specified by the value
of the ALERT_MAIL_ID package attribute, whenever there are critical
problems with the package.
Alert Notification Scriptv(SGAlert.sh)
This script is the interface between the Serviceguard package control script
and the Oracle toolkit.
Interface Script (toolkit.sh)
Table 3 Variable or Parameter Name in haoracle.conf file
DescriptionVariable/Parameter Name
This parameter determines whether the instance is an ASM instance or a database
instance. Set this parameter to database.
INSTANCE_TYPE
The home directory of Oracle.ORACLE_HOME
User name of the Oracle database administrator. This is used to start and stop the
database.
ORACLE_ADMIN
The Oracle session name. This is also called the session ID (SID). (for example,
ORACLE_TEST0) and uniquely identifies an Oracle database instance.
SID_NAME
This parameter defines the Oracle database startup mode. Valid options are "no
mount", "mount" and, "open". Default mode is "open".
START_MODE
Set to "yes" if you want this toolkit to start and stop the Oracle Listener.LISTENER
The names of the listener processes (typically the SID_NAME )LISTENER_NAME
The passwords of the listener processes.LISTENER_PASS
This parameter defines the number of attempts to be made to restart the listener. If the
listener does not restart after "LISTENER_RESTART" number of consecutive attempts,
LISTENER_RESTART
the package is failed over. If the listener restart is successful, then the next time listener
fails, the toolkit again tries "LISTENER_RESTART" number of times to restart the listener.
Oracle database parameter file. If you do not specify this parameter, Oracle picks
this up from the Oracle configuration directory $ORACLE_HOME/dbs. When this
PFILE
parameter is configured it overrides the default file/location. If both pfile and spfile
are present and this parameter left unspecified, then ECM Oracle Toolkit will make
use of pfile as the parameter file. To make use of spfile in the toolkit do not configure
this parameter and remove the default pfile from its default location.
The names of all processes that are running.MONITOR_PROCESSES
This variable enables or disables the maintenance mode for the Oracle database
package. By default this is set to "yes". To disable this feature MAINTENANCE_FLAG
MAINTENANCE_FLAG
must be set to "no". When Oracle Database or ASM requires maintenance, a
"<package directory>/oracle.debug" file must to be created. During this maintenance
period process monitoring for Oracle database or ASM monitoring is paused. Even
if an Oracle instance is brought down, its package is not failed over to the standby
node. To continue monitoring and return from the maintenance mode, remove the
oracle.debug file. You must ensure that Oracle instance is properly running after
the maintenance phase.
Support for Oracle Database Without ASM 15