DB2 FOR LUW / DB2FORLUW / A50 - DB2

db2fmp processes may be forced or terminated as part of normal 
processing.  Due to a timing condition, they may miss the 
request and end up lingering on the system as "unstable" db2fmp 
processes.  Over time the number of such processes may build, 
consuming excessive system memory, and affect the performance of 
the system and/or deplete paging space.

**************************************************************** 
* USERS AFFECTED:                                              * 
* systems using the Data Partitioning Feature (DPF)            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4                       * 
****************************************************************

Leftover unstable db2fmp processes can be identified by running 
"db2pd -fmp", and finding processes with a value of 0x00000830 
for "Flags".  They can be terminated using the db2fmpterm 
command. 
 
For example, in the following output, process 33882316 has a 
Flags value of 0x00000830, and can be terminated by issuing 
"db2fmpterm 33882316" 
Address            FmpPid     Bit   Flags      ActiveThrd 
PooledThrd ForcedThrd Active IPCList 
0x078000000414D5E0 33882316   64    0x00000830 0          0 
0          Yes    0x078000000414FBA0

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 Version 10.5 Fix Pack 4

see Local Fix

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

14.04.2014
22.09.2014
22.09.2014