home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC71067 Status: Closed

DB2FMP PROCESSES MAY NOT TERMINATE EVEN THOUGH THERE ARE NO ACTIVE THREADS
AND ARE MARKED FOR CLEANUP

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When running the db2pd -fmp command, you may see db2fmp 
processes that show zero active threads but are flagged for 
termination similar to the following: 
 
FMP Process: 
Address            FmpPid     Bit   Flags      ActiveThrd 
PooledThrd ForcedThrd Active IPCList 
0x0780000000D9ED00 729114     64    0x00000833 0          11 
    14         Yes    0x07800000007CFF40 
0x07800000018CE7C0 1413546    64    0x00000833 0          79 
    27         Yes    0x07800000007C0740 
0x078000000180E7C0 1261946    64    0x00000833 0          28 
    59         Yes    0x07800000007ECA00 
 
The following error message may also be seen in the db2diag.log: 
 
2010-04-14-22.19.07.617626-420 I53759020A333      LEVEL: Severe 
PID     : 569534               TID  : 2314        PROC : db2fmp 
(Java) 0 
INSTANCE: instname              NODE : 000 
EDUID   : 1234                 EDUNAME: db2fmp (Java) 0 
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpSendFini, 
probe:90 
RETCODE : ZRC=0x00000047=71
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW v9.7                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2FMP PROCESSES MAY NOT TERMINATE EVEN THOUGH THERE ARE NO  * 
* ACTIVE THREADS AND ARE MARKED FOR CLEANUP                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpack 4                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 LUW v9.7 Fixpack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.09.2010
02.05.2011
02.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList