DB2 FOR LUW / DB2FORLUW / A10 - DB2

Execution of 'db2fmcu -d' may terminate with return code 143. 
Following will be displayed in the DB2 command line upon 
execution of db2fmcu: 
 
# /db2/SB2/db2sb2_home/sqllib/bin/db2fmcu -d 
Terminated 
# echo $? 
143 
 
db2fmcu uses operating system call fcntl to check if file 
'/var/db2/.fmcd.lock' is locked by a running instance of the DB2 
fault monitor deamon (db2fmcd). 
If the file is locked a kill is sent to the PID returned by 
fcntl to finish the running db2fmcd process. 
 
It's been observed that the operating system might return PID 0 
for a locked file when fcntl is called. This could happen if the 
file is locaked on a shared filesystem (e.g. nfs). If the file 
is locked by a running process on machine A a call to fcntl on 
machine B will return the information that the file is locked 
but the PID will be 0. 
 
In case fcntl returns PID 0 db2fcmu does a kill against the 
process group and therefore terminates itself. 
This is not expected, hence db2fmcu needs to check the returned 
PID. A running db2fmcd process will always have a PID larger 
than 0.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FixPack 5                               * 
****************************************************************

First fixed in DB2 V10.1 FixPack 5

not known / see Local fix

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

03.06.2014
16.07.2015
16.07.2015