|
Problem IC84098
|
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 / A10 - 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: *
* Users making use of the SYSIBMADM.QUERY_PREP_COST *
* administrative view. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
This problem is resolved in DB2 version 10.1 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
31.10.2012
31.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
