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 IC68335 Status: Geschlossen

Counts for FCM metrics do not match wait times in row based interfaces

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In DB2 we count the number of FCM sends and receives, and also 
track any time we spend blocking during these sends and receives 
(FCM_SEND_WAIT_TIME). 
This can cause confusion as DB2 does not necessarily block on 
every send or recv. Therefore it is possible for the wait time 
to show up as zero even though FCM sends and receives had 
occurred and the counts are non-zero. 
 
To remedy this issue counters for each of the FCM 
times that represents the actual number of times we waited, as 
opposed to the number of times we performed a send or receive 
are exposed. 
 
FCM_SEND_WAITS_TOTAL 
FCM_RECV_WAITS_TOTAL 
FCM_MESSAGE_SEND_WAITS_TOTAL 
FCM_MESSAGE_RECV_WAITS_TOTAL 
FCM_TQ_SEND_WAITS_TOTAL 
FCM_TQ_RECV_WAITS_TOTAL
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In DB2 we count the number of FCM sends and receives,        * 
* andalsotrack any time we spend blocking during these sends   * 
* andreceives(FCM_SEND_WAIT_TIME).This can cause confusion as  * 
* DB2 does not necessarily blockonevery send or recv.          * 
* Therefore it is possible for the waittimeto show up as zero  * 
* even though FCM sends and receives hadoccurred and the       * 
* counts are non-zero.To remedy this issue counters for each   * 
* of the FCMtimes that represents the actual number of times   * 
* we waited,asopposed to the number of times we performed a    * 
* send orreceiveare                                            * 
* exposed.FCM_SEND_WAITS_TOTALFCM_RECV_WAITS_TOTALFCM_MESSAGE_SE 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP3                                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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

Lösung
First fixed in DB2 V9.7 FP3
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC70264 IT01835 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.05.2010
27.09.2010
27.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList