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

LOAD RESTART MIGHT INSERT INVALID TIMESTAMPS INTO TABLE WITH ROW CHANGE
TIMESTAMP COLUMNS

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
If a LOAD operation into a table with row change timestamp 
column fails (for whatever reason) within a small timing window 
near the beginning of the operation, a subsequent LOAD RESTART 
might complete successfully but insert invalid timestamps into 
the row change timestamp column, with values like 
 
0000-00-00-00.00.00.000001 
0000-00-00-00.00.00.000002 
0000-00-00-00.00.00.000003 
...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of LOAD + ROW CHANGE TIMESTAMP                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.8 Fix Pack 5.                   * 
****************************************************************
Local-Fix:
Do not use LOAD RESTART; do LOAD TERMINATE and then the original 
LOAD INSERT or LOAD REPLACE instead.
Lösung
Problem was first fixed in DB2 LUW Version 9.8 Fix Pack 5.
Workaround
see LOCAL FIX
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC83383 IC84572 IC84576 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.05.2012
06.07.2012
06.07.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP5
Problem behoben lt. FixList in der Version
9.8.0.5 FixList