|
Problem IC74071
|
Status: Closed |
ON WINDOWS LAST_METRICS_UPDATE FIELD OF PACKAGE CACHE ENTRIES AN DUPDATED_SINCE_BOUNDARY_TIME CAN BE OUT OF SYNC. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
On Windows the LAST_METRICS_UPDATE field of package cache
entries may not be in sync. It can be off by 1 to 2 seconds. The
consequence is that a package cache event monitor that uses the
WHERE UPDATED_SINCE_BOUNDARY_TIME option does not capture the
statement in certain cases where the LAST_METRICS_UPDATE is too
early. |
| Problem Summary: |
|
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Comment |
The problem is related to the timestamp on window. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.01.2011
28.04.2011
28.04.2011 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
