DB2 - Problembeschreibung
Problem IC94987 | Status: Geschlossen |
DPF: DB2DART REPORTED INDEX KEY ERRORS AFTER REDISTRIBUTE ON A TABLE WITH ADAPTIVE COMPRESSION | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DPF only * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 101 fp3 * **************************************************************** | |
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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in v101fp3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC94997 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.08.2013 27.09.2013 27.09.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |