|
Problem IC65288
|
Status: Closed |
INCORRECT TIMESTAMP IN THE WORKLOAD MANAGER (WLM) EVENT MONITOR TABLE WHEN A VIOLATION IS RECORDED |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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 |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V95 FP6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC68366 IC68367
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.12.2009
24.06.2010
24.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
