DB2 FOR LUW / DB2FORLUW / A10 - DB2

In a HADR/TSA environment where the DB2 instance name is a 
substring of the "db2V10_start.ksh" string, e.g. instance name = 
"db2", then the HADR resource reports as offline on both nodes. 
This is due to the following line within the hadrV10_monitor.ksh 
script: 
 
isInstanceStartRunning=$(ps -ef | grep db2V10_start.ksh | grep 
${candidate_P_instance?} | wc -l) 
 
The above checks for the existence of the db2V10_start.ksh 
process. In the case where the DB2 instance name is a substring 
of "db2V10_start.ksh" then the following result is returned: 
 
$ ps -ef | grep db2V10_start.ksh | grep db2 
db2inst1 17161 14568  0 15:32 pts/17   00:00:00 grep 
db2V10_start.ksh 
 
The hadrV10_monitor.ksh script interprets this result as if the 
db2V10_start.ksh process is currently running and returns 
2(Offline). In order to resolve this issue, the "grep 
db2V10_start.ksh" process must be filtered out from the results. 
Making the following change to the above line from the script 
fixes this: 
 
isInstanceStartRunning=$(ps -ef | grep db2V10_start.ksh | grep 
-v grep |grep ${candidate_P_instance?} | wc -l)

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 HADR/HA users                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5                              * 
****************************************************************

Make the following change to the 
/usr/sbin/rsct/sapolicies/db2/hadrV10_monitor.ksh script on both 
nodes: 
 
Replace this line: 
isInstanceStartRunning=$(ps -ef | grep db2V10_start.ksh | grep 
${candidate_P_instance?} | wc -l) 
with this line: 
isInstanceStartRunning=$(ps -ef | grep db2V10_start.ksh | grep 
-v grep | grep ${candidate_P_instance?} | wc -l)

Fixed in DB2 version 10.1.0.5

not known / see Local fix

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

13.11.2014
14.07.2015
14.07.2015