DB2 FOR LUW / DB2FORLUW / A50 - DB2

Many db2bp processes without parent process Id might be seen on 
ps command output. 
 
$ ps -ef | grep db2bp 
db2inst1   1625     1  0 May01 ?        00:00:00 /home/db2inst1 
/sqllib/bin/db2bp 1520A109 5 A 
db2inst1  13969     1  0 May01 ?        00:00:00 /home/db2inst1 
/sqllib/bin/db2bp 13777A109 5 A 
db2inst1  13986     1  0 May01 ?        00:00:00 /home/db2inst1 
/sqllib/bin/db2bp 13974A109 5 A 
db2inst1  23323     1  0 May04 ?        00:00:00 /home/db2inst1 
/sqllib/bin/db2bp 23226A109 5 A 
db2inst1  32551     1  0 May05 ?        00:00:00 /home/db2inst1 
/sqllib/bin/db2bp 32364A109 5 A 
db2inst1  32623     1  0 May05 ?        00:00:00 /home/db2inst1 
/sqllib/bin/db2bp 32611A109 5 A 
... 
 
Normally when the db2bp is idle, it will set an alarm to wake up 
every few seconds to see if parent process Id is still alive. 
When this parent process is gone, then the db2bp back-end 
process will clean itself up. 
 
There are situations when db2bp processes are not cleaned up 
even if db2 front-end process was terminated. 
This is because db2bp processes try to push large messages on 
the queues, which are blocked after that. 
 
db2bp processes cannot check if db2 parent process is still 
alive until  whole message from message queue is sent. 
If message queues get blocked this check cannot be done and 
db2bp processes remain in the system.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2LUW                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP7 or higher                            * 
****************************************************************

Increase kernel.msgmnb kernel parameter in /etc/sysctl.conf file 
for at least 512KB.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

08.01.2015
28.09.2016
28.09.2016