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 IT07439 Status: Closed

DB2PD -FMP SHOWS INCORRECT FORCEDTHRD VALUE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The value of ForcedThrd in the output of db2pd -fmp may be 
showing the incorrect value.  In the example output below, the 
ForcedThrd value is 138, but by looking at the "Forced Threads" 
heading below, it says "No forced threads" so the value should 
be zero. 
 
FMP Process: 
FmpPid     Bit   Flags      ActiveThrd PooledThrd ForcedThrd 
Active 
 55774      64    0x00000000 0          0          138        No 
 
 
   Active Threads: 
   No active threads. 
 
   Pooled Threads: 
     ThreadId : 0 
        Routine ID     Timestamp 
        66024          2015-02-13-00.44.49.637100 
 
   Forced Threads: 
   No forced threads.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.1 Users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 5 or higher.                   * 
****************************************************************
Local Fix:
To get the number of ForcedThrd, count the number of rows shown 
under the "Forced Threads" heading instead.
Solution
Fixed in DB2 V10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.03.2015
30.07.2015
30.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList