DB2 FOR LUW / DB2FORLUW / 970 - 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:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 8                        * 
****************************************************************

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 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in Version 9.7 Fix Pack 8

not known / see Local fix

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

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

12.12.2012
15.04.2013
15.04.2013

9.7.FP8