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 IC68094 Status: Geschlossen

FUTURE-DATED TIMESTAMPS REPORTED BY THE DEADLOCK MONITOR ON SOLARIS
X86-64

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
On the Solaris 64-bit platform, running on the x86-64 
architecture, when using the deadlock event monitor while 
running DB2, you might see timestamps that are future-dated, 
with respect to the system time, in the formatted event monitor 
output. 
 
Example: 
select current timestamp from sysibm.sysdummy1 
 
1 
-------------------------- 
2010-02-08-11.58.07.170382 
 
 
 450272) Deadlock statement history ... 
  Deadlock ID             : 0 
  Participant No          : 0 
  Application id          : *LOCAL.<instname>.xxxxxxx 
  Stmt history ID         : 502 
  Type                    : Dynamic 
  Section No              : 5 
  Package cache id        : 382252089561 
  Package creator         : NULLID 
  Package name            : SYSSH200 
  Package version         : 
  Lock timeout value      : 60 
  Nesting level of stmt   : 0 
  Invocation ID           : 0 
  Query ID                : 0 
  Source ID               : 0 
  UOW Sequence number     : 0001 
  Isolation level         : Cursor Stability 
  Stmt first use time     : 02/27/2010 15:13:26.876148 
  Stmt last use time      : 02/27/2010 15:13:26.877157 
  Statement text          : SELECT CREATE_TIME FROM 
SYSTOOLS.HMON_ATM_INFO WHERE SCHEMA = ? AND NAME = ? FOR UPDATE 
 
The "Stmt first use time" and "Stmt last use time" show 
future-dated timestamps when compared to the current timestamp 
on the server. This is a result of the underlying implementation 
used to generate the timestamp data. Note that the problem has 
only been seen with the deadlock event monitor, but may not be 
limited to it.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on Solaris X86-64                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* On the Solaris 64-bit platform, running on the               * 
* x86-64architecture, when using the deadlock event monitor    * 
* whilerunning DB2, you might see timestamps that are          * 
* future-dated,with respect to the system time, in the         * 
* formatted eventmonitoroutput.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 6 or use the local fixas * 
* a workaround                                                 * 
****************************************************************
Local-Fix:
If the time drift grows to be intolerably substantial over time, 
terminate all connections to the database, whose deadlock 
monitor exhibits this problem, and reconnect.
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 Version 9.5 Fix Pack 6
Workaround
If the time drift grows to be intolerably substantial over 
time, 
 
 
terminate all connections to the database, whose deadlock 
 
 
monitor exhibits this problem, and reconnect.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC68446 IC68447 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.04.2010
30.06.2010
30.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version