DB2 - Problembeschreibung
Problem IC65288 | Status: Geschlossen |
INCORRECT TIMESTAMP IN THE WORKLOAD MANAGER (WLM) EVENT MONITOR TABLE WHEN A VIOLATION IS RECORDED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
If a statement gets rejected due to the threshold limit having exceeded i.e a violation occurs , The TIME_STARTED contains a 0 value eg: db2 "select TIME_STARTED, TIME_COMPLETED from ACTIVITY_DB2ACTIVITIES where TIME_COMPLETED > current timestamp - 10 minutes" TIME_STARTED TIME_COMPLETED -------------------------- -------------------------- 0000-00-00-00.00.00.000000 2009-10-02-12.27.14.237480 This will cause nay date functions on that column to fail with SQL0443N | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users on lower versions than DB2 V95 FP6 * **************************************************************** * PROBLEM DESCRIPTION: * * INCORRECT TIMESTAMP IN THE WORKLOAD MANAGER (WLM) * * EVENTMONITORTABLE WHEN A VIOLATION IS RECORDED * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V95 FP6. * **************************************************************** | |
Local-Fix: | |
NA | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 V95 FP6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC68366 IC68367 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.12.2009 24.06.2010 24.06.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |