|
Problem IC65387
|
Status: Closed |
LOAD RESTART AFTER CRASH RECOVERY MAY CORRUPT TABLE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| 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.
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 Summary: |
****************************************************************
* 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) |
| available fix packs: |
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
|
| Solution |
First fixed in Version 9.5 Fixpack 6. At a minimum, this fix
should be applied on the server. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.01.2010
14.05.2010
14.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
