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

-901 IN REDISTRIBUTE ABORT AFTER SUCCESSFUL REDISTRIBUTE ABORT/CONTINUE
WITH EXCLUDE KEYWORD.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF environment only, after running REDISTRIBUTE             * 
* ABORT/CONTINUE command with EXCLUDE option.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 97 fix pack 9                         * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem fixed in v97 fix pack 9
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC95947 IC95948 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.09.2013
17.12.2013
17.12.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP9
Problem behoben lt. FixList in der Version
9.7.0.9 FixList
9.7.0.9 FixList