DB2 FOR LUW / DB2FORLUW / A10 - DB2

In a DB2 HA(TSA) environment, where partition 0 has designated 
failover nodes, the db2VXX_monitor.ksh script may falsely report 
that partition 0 is "Online" on one of its failover nodes. This 
causes the partition to be automatically stopped by TSA. 
 
There is a small window of time whereby the "ps -u" command will 
capture the "[db2sysc]" process in its output and falsely 
interpret it as partition 0's "db2sysc" process. The "[db2sysc]" 
process temporarily appears in the "ps -u" output after a 
partition's "db2sysc" process spawns and terminates one of its 
child processes.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 DPF HA(TSA) users                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 FP3                              * 
****************************************************************

Modify the appropriate db2VXX_monitor.ksh script so that it uses 
db2gcf instead of ps to monitor partition 0's status, i.e. make 
the following change: 
 
if [[ $NN -ne 0 ]]; then 
   bypassHomeDir=TRUE 
fi

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Fixed in DB2 version 10.1 FP3

not known / see Local fix

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

27.12.2012
01.10.2013
01.10.2013