home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC64810 Status: Closed

SNAPSHOT TIMESTAMP AND CURRENT TIMESTAMP MAY BE DIFFERENT ON SOME
MACHINES.

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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.7 FixPak 2                          * 
****************************************************************
Local Fix:
Not available.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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
Problem was first fixed in Version 9.7 FixPak 2
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67016 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.11.2009
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList
9.7.0.3 FixList
9.7.0.3 FixList