|
Problem IC67016
|
Status: Closed |
SNAPSHOT TIMESTAMP AND CURRENT TIMESTAMP MAY BE DIFFERENT ON SOME MACHINES. |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
Snapshot timestamp and current timestamp may be different on
some machines.
This time discrepancy may be seen in the timestamps in the DB2
Performance Expert.
The two timestamps are obtained from the different Windows APIs,
QueryPerformanceCounter() and GetLocalTime().
On some multi-core processor, if the Periodic SMI (System
Management Interrupt) is requested, one core is halted, the
timer is also halted. Then the timer between the cores leaps
every interrupt.
The timestamp from QueryPerformanceCounter() is synchronized
with the system time once at startup and is calculated using CPU
high-performance timer, while the timestamp from GetLocalTime()
is obtained from system time at every call.
Thus, the two timestamps may be different. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Windows user *
****************************************************************
* PROBLEM DESCRIPTION: *
* Snapshot timestamp and current timestamp can be different *
* onsome windows machines. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 Version 9.8 FixPak 3 *
**************************************************************** |
| Local Fix: |
Not available. |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Problem was first fixed in Version 9.8 FixPak 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.03.2010
22.12.2010
22.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
