home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT08198 Status: Geschlossen

DB2PD -FMP SHOWS INCORRECT FORCEDTHRD VALUE

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fixpack 7                                * 
****************************************************************
Local-Fix:
To get the number of ForcedThrd, count the number of rows shown 
under the "Forced Threads" heading instead.
Lösung
First fixed in DB2 10.5 Fixpack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.04.2015
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList