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

LOAD RESTART AFTER CRASH RECOVERY MAY CORRUPT TABLE

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
If a LOAD crashes the instance at a particular timing scenario, 
then after crash recovery, a LOAD RESTART on the table may 
silently corrupt the table. 
 
To potentially hit the error all of the following conditions 
must be met (error depends on timing, so even if all of the 
conditions are met the problem is still not guaranteed to 
happen): 
- table has at least one of: LF, LOB, XML columns 
- LOAD command has SAVECOUNT option specified 
- LOAD command has reached at least 1 savepoint during LOAD 
phase 
- LOAD command has crashed
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of DB2 Version 9.5                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a LOAD crashes the instance at a particular timing        * 
* scenario, then after crash recovery, a LOAD RESTART on the   * 
* table may silently corrupt the table.                        * 
*                                                              * 
* After crash recovery and issuing load RESTART, DB2 attempts  * 
* to restore an allocation page that no longer exists. This is * 
* due to log records not being flushed out before the crash.   * 
* The table is not corrupted when the LOAD crashes. It's only  * 
* when the user attempts a RESTART that data can be corrupted. * 
*                                                              * 
*                                                              * 
*                                                              * 
* To potentially hit the error all of the following conditions * 
* must be met (error depends on timing, so even if all of the  * 
* conditions are met the problem is still not guaranteed to    * 
* happen):                                                     * 
* - table has at least one of: LF, LOB, XML columns            * 
*                                                              * 
* - LOAD command has SAVECOUNT option specified                * 
*                                                              * 
* - LOAD command has reached at least 1 savepoint during LOAD  * 
* phase                                                        * 
*                                                              * 
* - LOAD command has crashed                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 Fixpack 6 or later                    * 
****************************************************************
Local-Fix:
Run LOAD TERMINATE followed by original LOAD command (no 
RESTART)
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in Version 9.5 Fixpack 6. At a minimum, this fix 
should be applied on the server.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.01.2010
14.05.2010
14.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version