DB2 Version 10.1 for Linux, UNIX, and Windows

DB2 High Availability Instance Configuration Utility (db2haicu) prerequisites

There is a set of tasks you must perform before using DB2® high availability instance configuration utility (db2haicu).

General

Before a database manager instance owner can run db2haicu, a user with root authority must run the preprpnode command.

preprpnode is part of the Reliable Scalable Cluster Technology (RSCT) fileset for AIX® and the RSCT package for Linux. preprpnode handles initializing the nodes for intracluster communication. The preprpnode command is run as a part of setting up the cluster. For more information about preprpnode, see:

preprpnode Command (AIX)
preprpnode command (Linux)

For more information about RSCT, see RSCT Administration Guide - What is RSCT?

Also, a user with root authority must disable the iTCO_wdt and iTCO_vendor_support modules.

On SUSE, add the following lines to the /etc/modprobe.d/blacklist file:
```
alias iTCO_wdt off
alias iTCO_vendor_support off
```
On RHEL, add the following lines to the /etc/modprobe.conf file:
```
blacklist iTCO_wdt
blacklist iTCO_vendor_support
```

You can verify that the modules are disabled by using the lsmod command.

Before running db2haicu, a database manager instance owner must perform the following tasks:

Synchronize services files on all machines that will be added to the cluster.
Run the db2profile script for the database manager instance that will be used to create the cluster domain.
Start the database manager using the db2start command.

Start of change For Linux, the End of change GNU C library (glibc) version must be 2.4-31.109.1 or higher.

DB2 high availability disaster recovery (HADR)

If you are using HADR functionality, perform the following tasks:

Ensure that both HADR databases exist on different systems.
Ensure all HADR databases are started in their respective primary and standby database roles, and that all HADR primary-standby database pairs are in peer state.
Ensure that you are using one of the following HADR synchronization modes: SYNC or NEARSYNC.
Configure hadr_peer_window for all HADR databases to a value of at least 120 seconds.
Disable the DB2 fault monitor.

Partitioned database environment

If you have multiple database partitions to configure for high availability, perform the following steps:

Configure the DB2_NUM_FAILOVER_NODES registry variable on all machines that are being added to the cluster domain.
(Optional) Activate the database before running db2haicu.