|
Problem IC84098
|
Status: Geschlossen |
SYSIBMADM.QUERY_PREP_COST ADMINISTRATIVE VIEW RETURNS A VALUE LARGER THAN 100 FOR THE PREP_TIME_PERCENT COLUMN. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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: |
|
| verfügbare FixPacks: |
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
|
| Lösung |
This problem is resolved in DB2 version 10.1 Fix Pack 1. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 12.06.2012
31.10.2012
31.10.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
