DB2 FOR LUW / DB2FORLUW / A50 - DB2

The "db2cluster -cfs -verify -maintenance" command hangs if the 
DEBUG environmental variable is set to 1, i.e. 
$ env | grep DEBUG 
DEBUG=1 
 
The process tree will show that the command is hanging within 
the mmgetstate process: 
     23554696  /opt/IBM/db2/V10.5_SB34072/bin/db2cluster -cfs 
-verify -maintenance 
        21023926    /usr/lpp/mmfs/bin/mmksh 
/usr/lpp/mmfs/bin/mmgetstate -Y -a 
 
The prockstack for the mmgetstate process may output similar to 
the following: 
----- 
procstack 21023926 
21023926: /usr/lpp/mmfs/bin/mmksh /usr/lpp/mmfs/bin/mmgetstate 
-Y -a 
0xd011fc84  write(??, ??, ??) + 0x1a4 
0x1002391c  sfwr(0x200016d0, 0x20034f90, 0x219, 0x0) + 0x51c 
0x10022d54  _sfflsbuf(0x200016d0, 0xffffffff) + 0x3d4 
0x100225a0  sfsync(0x200016d0) + 0x2a0 
0x10022214  _sfall() + 0x234 
0x10022328  sfsync(0x0) + 0x28 
0x100b8700  sh_fork(0x20a, 0x2ff11b14) + 0x40 
0x100bc4e0  sh_exec(0x2021fea8, 0x4) + 0x1e40 
  ... snip ... 
----- 
 
In order to avoid this issue the DEBUG environment variable must 
not be set to 1.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.5                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 FixPack 7.                           * 
****************************************************************

Unset the DEBUG environment variable by running "unset DEBUG".

Problem was first fixed in DB2 UDB Version 10.5 FixPack 7.

not known / see Local fix

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

24.06.2015
19.01.2016
29.04.2016