Attributes

Description

HADR_IP

Set the IP address used for performing the role switch.

 

Provide IP address from the subnet that is monitored by

 

Serviceguard

 

NOTE: This IP address should not be used to configure

 

HADR and the HADR must not use this IP for any

 

purpose. The format of this value should be as follows:

 

<IP_ADDRESS>:<SUBNET_ADDRESS>

 

For example: tkit/db2hadr/db2hadr/HADR_IP

 

10.76.1.200:10.76.1.0, where:

 

10.76.1.200 is the IP address

 

10.76.1.0 is the network subnet.

 

Suppose there are multiple subnets in the network,

 

HADR_IP must be defined for all the subnets.

 

For example: tkit/db2hadr/db2hadr/HADR_IP -

 

10.76.1.200:10.76.1.0

 

tkit/db2hadr/db2hadr/HADR_IP -

 

10.10.1.50:10.10.1.0

RESTORE_ROLE

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

 

both the primary and standby packages. If it is set to

 

[yes], the toolkit performs a role switch when both

 

primary and standby databases are in “peer” state but

 

the current role of the HADR is different from the

 

configured role of the package (HADR_ROLE package

 

attribute) on both nodes. This can happen when the

 

original primary goes down and a forced role takeover

 

is done by the standby, and later the primary comes up

 

as standby. The default value is [no].

vg

This attribute should be set if the database is on a

 

volume group. Configure this attribute, if the database

 

is on a local disk.

ip_address and ip_subnet

These attributes are assigned if the package is

 

configured to failover to another node. Also, when the

 

package fails over from one node to another node,

 

client traffic IP and interconnect IP must be moved to the

 

new node. Both the IPs must be defined in the package.

 

For a sample package configuration file, see “Sample

 

package configuration file for the DB2 HADR standby

 

package” (page 52)

 

For DB2 Service

service_name

Name of the service that Serviceguard monitors while

 

the package is up. This name must be unique for both

 

primary and standby packages in a Serviceguard

 

cluster. The default value is db2_service.

service_cmd

It is the command line to start the service. $SGCONF/

 

scripts/ecmt/db2/tkit_module.sh

 

db2_monitor.

service_restart

This attribute specifies the number of times the service

 

was restarted before failing. The default value is [none].

service_fail_fast_enabled

This attribute enables Serviceguard to halt the node if

 

the service fails on that node. The default value is set to

 

[no].

service_halt_timeout

It is used to determine the duration for which

 

Serviceguard waits for the service to halt before a

 

SIGKILL signal. The default value is [300 seconds].

 

Using the DB2 HADR toolkit 41

Page 41
Image 41
HP Serviceguard Toolkits for Database Replication Solutions manual Hadrip