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 are using this configuration, you must see the 'PFILE' parameter in the haoracle.conf
configuration file to the specific pfile on a given host. For example, the PFILE in haoracle.conf on
node1 must be set to /ORACLE_TEST0/dbs/initORACLE_TEST0.ora.node1.
Error Handling
On startup, the Oracle shell script checks for the existence of the init${SID_NAME}.ora or
spfile${SID_NAME}.ora file in the shared ${ORACLE_HOME}/dbs directory. If this file does not
exist, the database cannot be started on any node until the situation is corrected. The Oracle shell
script halts the package on that node and tries to start it on the standby node.
Network Configuration
This document does not cover detailed instructions on how to configure the Oracle network products
for a Serviceguard cluster. This section contains few basic suggestions on how to configure a
TCP/IP listener for a clustered environment. For a detailed description on how to set up the
networking products.
Entries:
• /etc/hosts
If you want to access your Oracle instance through a 'hostname', you must add entries for the
relocatable IP-addresses to your /etc/hosts file (or nameserver). This allows you to connect to your
database using a logical name with a telnet or rlogin. Therefore, /etc/hosts contain names of
services (database servers) in addition to real physical hostnames. From Serviceguard's point of
view, these are relocatable hostnames:
EXAMPLE:
If, a Serviceguard package for the Oracle instance ORACLE_TEST0 is assigned the IP address
192.10.10.1
Add the following entry to your hosts files:
192.10.10.1 ORACLE_TEST0
You can now reach 'ORACLE_TEST0' instance using the name 'ORACLE_TEST0' regardless of the
node on which it is running.
Listener
Set up a listener process for each Oracle instance that executes on a Serviceguard cluster, make
sure that the listener can move with the instance to another node. Effectively, ensure the listener
configured to a specific Oracle instance is assigned to a unique port.
In the current release you can configure one listener to be monitored by the toolkit.
However, you can configure multiple listeners for the Oracle instance outside the Serviceguard
environment to provide more HA to the listener.
NOTE: HP recommends that you to use encrypted passwords for password protected listeners.
Copy the password specified for a listener in the parameter PASSWORDS_<listener_name> in
the file LISTENER.ORA, to the LISTENER_PASS parameter in the haoracle.conf file. If there are
multiple passwords configured for a single listener, you can use any one of them for the
LISTENER_PASS parameter in the haoracle.conf.
For Oracle 10g and 11g, there is a new listener feature called "Local OS Authentication" that is
activated by default. With this feature you can administer the listener without password
authentication. To disable this feature, you need to specify
"LOCAL_OS_AUTHENTICATION_listener_name = OFF" in LISTENER.ORA. For Oracle 10g, you
must specify the plain text password for the LISTENER_PASS parameter in haoracle.conf
(and not the encrypted password found in LISTENER.ORA).
Error Handling 55