DB2 FOR LUW / DB2FORLUW / 950 - DB2

HADR monitor script may timeout and return UNKNOWN during 
reintegration, when under heavy load. 
 
The timeouts happen because the instance is in the process of 
starting and the monitor script, which runs for each database 
every 21 seconds, is adding additional load by executing "db2gcf 
-s" and "db2 force application". Both of these 
commands are irrelevant if the instance is not started. 
 
This APAR fix will do two things to avoid HADR monitor script 
timeouts during reintegration, when under heavy load - 
 
1. HADR monitor script will return Offline if instance is not 
started 
2. Dynamically determine timeout for "db2gcf -s" based on HADR 
monitor script timeout

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V95 HA (HADR) users                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Reintegration under heavy load (many dbs) fails due to HADR  * 
* monitor script timeouts (returns UNKNOWN)                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V95FP8                                            * 
****************************************************************

DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

Modify HADR monitor script to return Offline is instance has not 
started 
Determine timeout for "db2gcf -s" dynamically, based on HADR 
monitor script timeout

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC74660 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

23.02.2011
27.06.2011
27.06.2011

9.5.FP8