home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC64810 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.7 FixPak 2
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67016 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.11.2009
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.2 FixList
9.7.0.3 FixList
9.7.0.3 FixList