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:
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.
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.
DB2 High Availability
Disaster Recovery (HADR)
If you will be using HADR functionality,
perform the following tasks:
- Ensure all DB2 High Availability
Disaster Recovery (HADR) databases are started in their respective
primary and standby database roles, and that all HADR primary-standby
database pairs are in peer state.
- Configure hadr_peer_window for all HADR databases
to a value of at least 120 seconds.
- Disable 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 will be added to the cluster domain.
- (Optional) Activate the database before running db2haicu.