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

DB2TOP GRANULARITY IN BACKGROUND MODE for database metrics

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The granularity ( precise ) of AvgPoolReadTime, AvgDirReadTime, 
AvgPoolWriteTime and AvgDirWriteTime in db2top background mode 
for database metrics ( e.g. db2top -d <dbname> -b d ) 
is only millisecond, so it won't be able show the granularity 
less than 1 millisecond. 
Intention of this APAR is to extend granularity to microsecond ( 
the measure unit will still be millisecond, the micro value will 
be shown by three decimal places after dot: e.g. 0.224 ms, 9.150 
ms )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************
Local Fix:
available fix packs:
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

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