DB2 FOR LUW / DB2FORLUW / A50 - DB2

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).

**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 4                               * 
****************************************************************

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Fixed in v105fp4

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

13.09.2013
15.09.2014
15.09.2014