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

THE ELAPSED TIME SHOWN IN DB2TRC FLOW OUTPUT FILE COULD BE WRONG WHEN
"-T" AND "-P" ( AND/OR "-M" ) OPTIONS ARE
SPECIFIED.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When "db2trc flw" the trace dump file with "-t" and "-p" ( 
and/or "-m" ) options specified, the elapsed time shown in 
db2trc flow output file for each record could be wrong in most 
of cases.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* THE ELAPSED TIME SHOWN IN DB2TRC FLOW OUTPUT FILE COULD BE   * 
* WRONG                                                        * 
* WHEN "-T" AND "-P" ( AND/OR "-M" ) OPTIONS ARE SPECIFIED.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 Fixpack 6                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.5 Fixpack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC63913 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.10.2009
13.05.2010
13.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)