DB2 - Problem description
Problem IC68573 | Status: Closed |
DB2FMP PROCESSES MAY NOT TERMINATE EVEN THOUGH THERE ARE NO ACTIVE THREADS AND ARE MARKED FOR CLEANUP | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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.5 * **************************************************************** * PROBLEM DESCRIPTION: * * DB2FMP PROCESSES MAY NOT TERMINATE EVEN THOUGH THERE ARE * * NOACTIVE THREADS AND ARE MARKED FOR CLEANUP * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW v9.5 Fixpak 7 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 LUW v9.5 Fixpak 7 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC71067 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.05.2010 15.11.2010 15.11.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.7 | |
9.5.0.7 |