|
Problem IC62777
|
Status: Closed |
NEXT KEY LOCKING ISSUE MAY RESULT IN INDEX CORRUPTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
There is an internal problem in the index manager next key
locking code which may cause index corruption. While inserting
keys, index manager may sometimes encounter a non-severe error.
For example, insert may fail because index node is full and
needs to be split. In this case, index manager will retry the
insertion after the node has been split. The problem here is
that due to an incorrect check, the index manager may sometimes
overwrite the non-severe error, and it could continue inserting
keys on an index node which is not locked thereby opening a
possibility for corruption. |
| Problem Summary: |
The problem is that under the conditions described above, the
index manager may write to an index page which is not locked in
memory. As a result, this page may get overwritten and flushed
to disk as such causing the index corruption. |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The APAR fix for this issue was inluded in DB2 V9.7 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.08.2009
18.02.2010
18.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
