Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX Release README: B.06.00

ManualsBrandsHP ManualsSoftwareHP Serviceguard Enterprise Cluster Master Toolkit

Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX

=========================================================================

Version: B.06.00

CONTENTS:

A. Overview

B. DB2 Information

C. Setting Up the Application

D. Setting Up the Toolkit

E. DB2 Package Configuration Example

F. Adding the Package to the Cluster

G. Database Maintenance

PREFACE:

DB2 is a RDBMS product from IBM. This README file describes

the High

Availability toolkit for DB2 v9.5 and v9.7 designed to be used

Serviceguard environment.

This document covers the basic steps to configure DB2 v9.5 and

v9.7

instances in Serviceguard cluster.This document is intended only for

users

who want to integrate DB2 v9.5 and v9.7 Database Server with HP

Serviceguard

11.19 in HP-UX environments.

This document assumes that the readers are already familiar with

Serviceguard

configuration, as well as with DB2 database server concepts,

including

installation & configuration procedures.

NOTE: Unless otherwise stated, this toolkit runs on all HP-UX

distributions

and all hardware supported by Serviceguard.This toolkit works with DB2

9.1

also. Multiple partitions are supported only with DB2 v9.1.

A.Overview

The DB2 Database Toolkit for Serviceguard consists of a set

of shell scripts that are used to start, stop, and monitor DB2 database

instances.This toolkit can be used with legacy and modular style of

packages.

Subsequent sections (D, E, F sections) of this document provide

guidelines for integrating this toolkit with Serviceguard package

control

script (for legacy packages), or with the master control script

(for modular packages).

Summary of content (17 pages)

PAGE 1
Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX ========================================================================= = Version: B.06.00 CONTENTS: A. B. C. D. E. F. G. Overview DB2 Information Setting Up the Application Setting Up the Toolkit DB2 Package Configuration Example Adding the Package to the Cluster Database Maintenance PREFACE: DB2 is a RDBMS product from IBM. This README file describes the High Availability toolkit for DB2 v9.5 and v9.
PAGE 2
NOTE: This README file assumes that the user has already installed Serviceguard, DB2 Database, and the DB2 Database toolkit on all cluster nodes. B.DB2 Information Each cluster member requires a local copy of DB2 server. DB2 instances are configured as packages under Serviceguard. Clients connect to the DB2 database using an IP address that is assigned to the Serviceguard package. Serviceguard monitors the health of the DB2 Database Server using DB2 Database utility tool "db2gcf".
PAGE 3
deferring the instance creation. The destination directory for DB2 server must be the same on all cluster nodes. DB2 installation must be done by a root user. 4. Modify the Kernel parameters if required. IBM provides /opt/IBM/DB2/V9.5/bin/db2osconf utility to aid administrators in determining the minimum recommended kernel values for DB2 server. As root, /opt/IBM/DB2/V9.5/bin/db2osconf or /opt/IBM/DB2/V9.
PAGE 4
7. Share (export) instance owner home directory (/home/payroll_inst in this case) to make it available to all cluster members. NFS example is shown below. [root@node1/]> share -F nfs /home/payroll_inst 8. 6. On the remaining cluster nodes mount the directory exported in step [root@node2/]> mount .F nfs node1:/home/db2inst1 /home/db2inst1 9. DB2 In case of multi partitioned database installation , edit node configuration file (db2nodes.
PAGE 5
As Instance owner execute the following. [payroll_inst@node1/]> db2set DB2COMM=tcpip [payroll_inst@node1/]> update database manager configuration using svcename db2c_payroll_inst [payroll_inst@node1/]> db2stop [payroll_inst@node1/]> db2start 11. Start database manager and examine the database log for any errors. [payroll_inst@node1 ~]> db2start 07/15/2008 18:10:32 1 0 SQL1063N DB2START processing was successful. 04/15/2008 18:10:32 0 0 SQL1063N DB2START processing was successful.
PAGE 6
located at http://publib.boulder.ibm.com/infocenter/db2luw/v9/ topic/com.ibm.db2.udb.admin.doc/doc/c0008221.htm NOTE: The above steps from 1 to 12 have to be repeated on all nodes in the cluster. Above steps 5 to 10 are applicable for multi-partition database setup. Single partition users need not defer the instance creation while installing as mentioned in step 4.
PAGE 7
or for use with Asynchronous disk access and file systems: /dev/vg01_payroll/lvol1 /dev/vg02_payroll/lvol1 /dev/vg03_payroll/lvol2 #Logical volume DB2 data #Logical volume DB2 data #Logical volume DB2 data D. Setting Up the Toolkit - Toolkit Overview After installing this toolkit, three scripts and this README file will be present in the /opt/cmcluster/toolkit/db2/ directory. Two more scripts and one Attribute Definition File will be present which will be used only by modular packages.
PAGE 8
PARTITION_NUMBER: partitions that The list of the participate in logical database a DB2 instance and are intended to run on single server. Physical partitions should be packaged separately. MONITOR_PROCESSES: processes of This is the failsafe list of critical a DB2 instance. Note:-These processes must not be running after DB2 is shutdown. If the processes are still running they will be killed by sending a SIGKILL.
PAGE 9
the package directory will put the package in toolkit maintenance mode. Serviceguard 11.19 release has a new feature which allows individual components of the package to be maintained while the package is still up. This feature is called Package Maintenance mode and is available only for modular packages. For more information on using Package Maintenance mode, refer the whitepaper "Modular package support in Serviceguard for Linux and ECM Toolkits" located at http://docs.hp.com/en/ha.
PAGE 10
This script contains a list of internally used variables and functions for monitoring a DB2 server instance. This script will be called by hadb2.sh. It uses a tool called "db2gcf" to monitor the database. - Interface Script (toolkit.sh) This script is the interface between the Serviceguard package control script and the DB2 toolkit. NOTE: The following modular method of packaging.
PAGE 11
E. DB2 Package Configuration Example - Package Setup and Configuration 1. Assuming DB2 is already installed. Follow the instructions in the chapter "Building an HA Cluster Configuration" in the "Managing ServiceGuard" manual to create a logical volume infrastructure on a shared disk. The disk must be exposed to all clustered nodes that will be configured to run this database instance.
PAGE 12
Repeat this step on all other clustered nodes to be configured to run the package to ensure DB2 can be brought up and down successfully. NOTE: creating Following steps in this section describe the method for Serviceguard package using the legacy method. For information on creating Serviceguard package using modular method, please refer to white paper "Modular package support in Serviceguard for Linux and ECM Toolkits" located at http://docs.hp.com/en/ha.html 4.
PAGE 13
Note that one of these file systems must be the shared file system/logical volume containing the DB2 home configuration information ($DB2_HOME). The name of the instance is used to name the volume groups, logical volumes and file systems. EXAMPLE: LV[0]=/dev/vg0_payroll/lvol1 FS[0]=/mnt/payroll The service name must be the same as defined in the package configuration file. Always call the toolkit.sh script with "monitor" for the SERVICE_CMD definitions.
PAGE 14
- The Serviceguard package configuration file (pkg.conf). The package configuration file is created with "cmmakepkg -p", and should be put in the following location: '/etc/cmcluster/pkg/db2_pkg/' EXAMPLE: /etc/cmcluster/pkg/db2_pkg/pkg.conf The configuration file should be edited as indicated by the comments in that file. The package name needs to be unique within the cluster. For clarity, use the name of the database instance to name the package.
PAGE 15
In the package directory, modify the hadb2.conf configuration file for this DB2 instance. Example: Edit the hadb2.conf as indicated by the comments in that script. For Example, INSTANCE_NAME=db2_payroll_inst PARTITION_NUMBER[0]=0 PARTITION_NUMBER[1]=1 MONITOR_PROCESSES[0]=db2sysc MONITOR_PROCESSES[1]=db2acd MAINTENANCE_FLAG=YES MONITOR_INTERVAL=30 TIME_OUT=30 After setting up the Serviceguard environment, each clustered DB2 instance should have the following files in the related package directory. E.g.
PAGE 16
There might be situations, when the DB2 database has to be taken down for maintenance purposes like changing configuration, without having the instance to migrate to standby node. The following procedure should be used: Note: The example assumes that the package package directory is /etc/cmcluster/pkg/db2_pkg. name is db2_payroll, - Disable the failover of the package through cmmodpkg command.
PAGE 17
The message "Starting DB2 toolkit monitoring again after maintenance" appears in the Serviceguard Package Control script log. - Enable the package failover $ cmmodpkg -e db2_payroll Note: If the package fails during maintenance (e.g., the node crashes), the package will not automatically fail over to an adoptive node. It is the responsibility of the user to start the package up on an adoptive node. Please refer to the manual "Managing Serviceguard" for more details.