|
Problem IC81150
|
Status: Closed |
DUPLICATE RECORDS AFTER REDISTRIBUTE ABORT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
While running, redistribute creates control files to keep track
of the redistribute progress and know where to resume the
redistribute in case of a failure.
There exists a timing hole where a database partition can
receive data but the control file isn't kept on disk. In case of
a failure and a REDISTRIBUTE ABORT operation we can replay the
data and end up with duplicate records.
The problem is hard to hit and only encountered during a
REDISTRIBUTE ABORT operation. Only the table being processed at
the time of the redistribute failure is affected. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of REDISTRIBUTE ABORT *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 V9.7 Fix Pack 6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
Fixed in DB2 V9.7 Fix Pack 6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC81672 IC84581
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.02.2012
05.06.2012
05.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
