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
MIG29
master tcp ether mig29 5000
query tcp ether mig29 5000
For a re-locatable IP-address, you must edit this interface entry, as follows:
MIG29
master tcp ether 192.168.10.1 5000
query tcp ether 192.168.10.1 5000
If you require a re-locatable hostname to be associated with this re-locatable IP-address, do the
followingf:
1. Use the re-locatable hostname in the srvbuild.adaptive_server.rs and similar files for all the
other 'server' processes and use srvbuildres utility to configure the servers.
2. Make the (relocatable_,P relocatable_hostname) pairs entry in the /etc/hosts (and also in the
nameserver, if necessary). The /etc/hosts, must contain the <IP-address, hostname> associated
with each ASE instance along with the physical IP-address and corresponding physical
hostname entries.
- /etc/hosts
Ensure that the entries mentioned above are present in the /etc/hosts file before an attempt
is made to bring up the ASE processes.
For example, consider that the IP 192.168.10.1 is the associated IP and sybase0 is the
associated hostname with the ASE instance SYBASE0. The entry required in /etc/hosts is:
192.168.10.1 sybase0
In the adaptive server configuration file, the re-locatable hostname sybase0 must be used in
place of the hostname:
sqlsrv.network_hostname_list: PUT_YOUR_HOSTNAME_HERE
as -
sqlsrv.network_hostname_list: sybase0
NOTE: If you don not want to use a re-locatable hostname with the ASE instance, the /etc/
hosts file on each node must contain the re-locatable IP-address associated with the physical
hostname of that node. For example, if node1_hostname and node2_hostname are the physical
hostnames of two nodes in the cluster, and if 192.168.10.1 is the re-locatable IP-address for
the ASE instance, the /etc/hosts of node1 must have an entry like: 192.168.10.1
node1_hostname
And the /etc/hosts file of node2 have an entry like: 192.168.10.1 node2_hostname.
Database Maintenance
There might be situations, when the Sybase ASE database must to be taken down for maintenance
purposes like changing configuration, without migrating the instance to standby node. To take
down the database:
NOTE: The example assumes that the package name is SYBASE0, the package directory is
/opt/cmcluster/pkg/SYBASE0, and the SYBASE_HOME is configured as /SYBASE0.
1. To disable the failover of the package, run the following command:
$ cmmodpkg -d SYBASE0
2. Pause the monitor script.
Create an empty file <TKIT_DIR>/sybase.debug
$ touch <TKIT_DIR>/sybase.debug
72 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX