|
Problem IC95947
|
Status: Closed |
-901 IN REDISTRIBUTE ABORT AFTER SUCCESSFUL REDISTRIBUTE ABORT/CONTINUE WITH EXCLUDE KEYWORD. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The problem is specific to EXCLUDE clause on ABORT/CONTINUE
operation.
There are two similar problems, both lead to complete table
data loss.
1. If two tables have to be recovered, then a successful
recovery of just one (second is EXCLUDEd) clears recovery info
about the second one. The second table is left in limbo - it
can't be
recovered from redistribute, and can't be accessed.
2. If two tables have to be recovered, but one failed when
redistribute was going in CONTINUE direction and another failed
when redistribute was going in ABORT direction, then
redistribute recovery can't recover one of the two.
==
Sample scenario (assume two tables, t1 and t2):
REDISTRIBUTE ADD NODE - failed while redistributing table t1
REDISTRIBUTE ABORT EXCLUDE T1 - failed while redistributing t2
At this point both tables require redistribute recovery, and
either recovery info from one of them will be removed (if
EXCLUDE clause is specified), or only one is recovered (if no
EXCLUDE clause is specified). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DPF *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 101 fp4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Error -6056 with reason code 17 is returned. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.09.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
