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

RECOVERING A FAILED ONLINE INCREMENTAL LOAD ON AN INDEX CREATED WITH THE
"PCTFREE 0" OPTION MIGHT CORRUPT THE INDEX

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
This applies to any databases with the above specific condition. 
 
The problem can happen only if the index in question is defined 
with the "PCTFREE 0" 
option.  Then an online incremental load must be performed. 
During a very specific internal error scenario  and recovery, 
there is a chance that the index page could get corrupted 
and we end up with duplicate keys  on the page. 
 
Symptoms may include index-data mismatch or incorrect results. 
 
Running db2dart or inspect may be able to detect the problem. 
Look for duplicate key or key data mismatch error messages.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.4.                             * 
****************************************************************
Local-Fix:
To avoid hitting this problem as opposed to undo the corruption, 
the user can use db2dart /mi option to mark the index bad before 
recovering the failed load command. 
 
Applying the APAR fix will prevent the problem from occurring. 
 
If this problem is hit and the index is corrupted, then the 
solution is to use db2dart /mi to mark the index invalid and 
then the next access to the table will rebuild the index.
verfügbare FixPacks:
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

Lösung
The problem is first fixed in DB2 version 10.5.0.4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.07.2014
08.09.2014
26.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList