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

DBSUMMARY() METRICS BREAKDOWN MAY REPORT INACCURATE VALUES FOR
POOL_READ_TIME OR POOL_WRITE_TIME COMPARED TO TOTAL_WAIT_TIME

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
monreport.dbsummary() metrics breakdown may report higer values 
for POOL_READ_TIME or POOL_WRITE_TIME (more than 100%) compared 
to TOTAL_WAIT_TIME 
 
example snip-it: 
 
 -- Detailed breakdown of TOTAL_WAIT_TIME -- 
 
                                %    Total 
                                --- 
--------------------------------------------- 
  TOTAL_WAIT_TIME               100  894476 
 
  I/O wait time 
    POOL_READ_TIME              138  1237563
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.10.2013
25.06.2014
25.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList