DB2 FOR LUW / DB2FORLUW / A50 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* all platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V105 FP3                                      * 
****************************************************************

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

DB2 V105 FP3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

16.05.2014
10.03.2015
10.03.2015