HP Serviceguard Toolkits for Database Replication Solutions manual Instancename

Page 40

4.Edit the following attributes manually in this file before creating the package:

Attributes

package_name package_type node_name

Description

The package name must be unique in the cluster.

Package must be a failover package.

Name of the cluster node on which the package will run. Ensure that the primary package and the standby package have different node names. The primary and the standby packages must not run on the same node.

script_log_file

It is the package log file path where the package log is

 

stored.

TKIT_DIR

This is the package directory where the toolkit

 

configuration files are generated when the package is

 

created. This directory need not be same for the Primary

 

and the Standby packages.

ALERT_MAIL_ID

It is the administrator’s email ID. The package sends

 

alert mails during package failure.

INSTANCE_NAME

It is the DB2 instance name (e.g. db2inst1)

PARTITION_NUMBER

Set it to 0 since DB2 HADR toolkit does not support

 

multiple partitions. The default value is 0.

MONITOR_PROCESSES

The default value is db2sysc. Do not change this value.

MAINTENANCE_FLAG

This attribute is used to enable or disable the

 

maintenance mode. The default value is [yes].

MONITOR_INTERVAL

This is the time interval (in seconds) between the monitor

 

cycles and the default value is 30 seconds. The toolkit

 

monitors the health of the package every

 

[MONITOR_INTERVAL ]seconds.

 

NOTE: This value adds to the time for role takeover

 

and hence should be set to an optimum value.

TIME_OUT

This value is used when a package is halted. During

 

this time the toolkit awaits the completion of a normal

 

package shutdown before forcefully halting the

 

application.

HADR_ROLE

Set it either to [primary] or [standby] based on the role

 

that the HADR is supposed to play on the node.

HADR_DATABASE

This is the DB2 database name on which HADR is

 

configured.

ROLE_MANAGEMENT

Set it either to [yes ]or [no]. The value must be same for

 

both the primary and standby packages. If this attribute

 

is set to [yes ]then package handles role takeover and

 

final role switch. If it is set to [no ]then package does

 

not handle role takeover and final role switch. It can

 

only function as a failover package. The default value

 

is set to [no].

 

NOTE: If this attribute is set to [yes ]then HADR_IPand

 

RESTORE_ROLE attributes must be defined.

40 Serviceguard toolkit for DB2 High Availability Disaster Recovery

Image 40
Contents HP Part Number Published August Edition Page Contents Glossary Index Introduction Overview AdvantagesDependencies Supported configurationSingle-instance Oracle database Cmmakepkg -i pkgasciifile -m modulefilename outputfilename RAC environment RAC environmentServiceguard toolkit for Oracle Data Guard Data Guard replication between RAC primary and RAC standby Continentalclusters environment Continentalclusters environment Metrocluster and extended distance cluster environments Supported configuration Data Guard setup in an EDC environment Three data center configuration Configuring multiple instances of Oracle Data Guard Multiple Data Guard instances in each Serviceguard clusterSetting up Oracle Data Guard toolkit Installing and uninstalling Oracle Data Guard toolkit# swinstall -s depot path High availability for data guard broker# swlist -l product T2259AA Files for the ADF module Activestandby Configuring Oracle Data Guard toolkit Package attributesSingle-instance environment For example, /etc/cmcluster/pkg/dgpkgSetting up Oracle Data Guard toolkit #ecmt/oracle/oracle/LISTENERRESTART Servicefailfastenabled no servicehalttimeout RAC environment For example, /etc/cmluster/pkg/racdgpkgWhere ocmnp is the Smnp package for Oracle CLusterware Adding the package to the Serviceguard cluster Maintaining Oracle Data Guard toolkitCluster verification for Oracle Data Guard toolkit Single-instance environmentPkg.conf command TroubleshootingLimitations Startstandbyasprimary to yes Prerequisites Using the DB2 Hadr toolkit Supported configurationWhen primary and standby packages are in the same cluster Event 1 Standby database or Hadr goes downEvent 2 Primary package fails When primary and standby packages are in different clusters Primary and Standby Packages in Different ClustersCreating packages To provide high availability only to primary databaseGo to the /etc/cmcluster/hadrprimary directory Cmmakepkg -m ecmt/db2/db2 -m tkit/db2hadr/db2hadr pkg.confInstancename Hadrip Managing packages Running packagesMaintaining packages And, $ cmmodpkg -e hadrpkgHalting packages # cmhaltpkg packagenameHost key verification failed. Lost connection Limitations How to contact HP Information to collect before contacting HPWarranty information HP authorized resellersDocumentation feedback Related information Typographic conventionsTIP Db2 get db cfg for db2 database name grep -i hard Node3# /usr/bin/ssh-keygen -t rsaNode3# /usr/bin/ssh-keygen -t dsa Node2# /usr/bin/ssh-keygen -t rsaPage To add a new key to/home/user/.ssh/knownhosts Page Glossary Index