DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V9.7 users                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 11 or higher.                   * 
****************************************************************

Fixed in DB2 V9.7 Fix Pack 11

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

14.06.2015
07.10.2015
07.10.2015

9.7.FP11