home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC94997 Status: Closed

DPF: DB2DART REPORTED INDEX KEY ERRORS AFTER REDISTRIBUTE ON A TABLE WITH
ADAPTIVE COMPRESSION

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
After successful REDISTRIBUTE operation (not all apply, see Note 
1:) on a table that has ADAPTIVE COMPRESSION enabled, table may 
become corrupt. Some records may appear twice (no more than 
twice) in table, but will be listed correctly (always once) in 
the index. 
 
Symptoms are either 
- db2dart errors saying that INX object has less records than 
DAT object, 
- table scan returns more rows than index scan 
 
Note 1: corruption can happen only on existing node that 
receives some data from another node as part of REDISTRIBUTE 
operation. That means DROP NODE, or rebalance. 
Unless target partition map is provided explicitly, REDISTRIBUTE 
ADD NODE is not affected by this corruption.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 Fix Pack 4                       * 
****************************************************************
Local Fix:
Index contains correct info. EXPORT all data (SELECT *) from the 
table, prune it based on index entries. To do that export table 
data based on index scan and match record by record to the first 
output. 
 
Then DROP TABLE, re-create it, and populate from pruned file.
available fix packs:
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

Solution
Fixed in v105fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.08.2013
15.09.2014
15.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList