|
Problem IC68335
|
Status: Closed |
Counts for FCM metrics do not match wait times in row based interfaces |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
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
|
| Solution |
First fixed in DB2 V9.7 FP3 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC70264 IT01835
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.05.2010
27.09.2010
27.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
