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

SYSIBMADM.QUERY_PREP_COST ADMINISTRATIVE VIEW RETURNS A VALUE LARGER THAN
100 FOR THE PREP_TIME_PERCENT COLUMN.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When the worst prepare time for a statement as reported by the 
PREP_TIME_WORST monitor element is less than a millisecond, the 
monitor element is incorrectly reported as 1 millisecond. This 
can result in the SYSIBMADM.QUERY_PREP_COST administrative view 
returning a percentage larger than 100 for the PREP_TIME_PERCENT 
column. For example if the execution time for a statement 500 
microseconds (which includes the prepare time) and the prepare 
time was 100 microseconds, the PREP_TIME_WORST monitor element 
will be incorreclty reported as 1 millisecond rather than 
truncated to 0, and the PREP_TIME_PERCENT column in 
SYSIBMADM.QUERY_PREP_COST would report 200% for the statement.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V9.7 users                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 11 or higher.                   * 
****************************************************************
Local Fix:
Solution
Fixed in DB2 V9.7 Fix Pack 11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2015
07.10.2015
07.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList