|
Problem IC83383
|
Status: Closed |
LOAD RESTART MIGHT INSERT INVALID TIMESTAMPS INTO TABLE WITH ROW CHANGE TIMESTAMP COLUMNS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of LOAD + ROW CHANGE TIMESTAMP *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW Version 10.1 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
Do not use LOAD RESTART; do LOAD TERMINATE and then the original
LOAD INSERT or LOAD REPLACE instead. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 LUW Version 10.1 Fix Pack 1. |
| Workaround |
see LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.05.2012
01.11.2012
01.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
