|
Problem IC87500
|
Status: Closed |
ROWS MIGHT BE INSERTED INTO WRONG MDC TABLE CELL AFTER PREVIOUS INSERTS IN SAME TRANSACTION ENCOUNTER TABLESPACE FULL |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If inserts into the MDC table encounter tablespace full, the
subsequent inserts within the same transaction, with same block
index values, might place rows into the wrong MDC table extent.
The problem only occurs if after encountering the error during
insert, the transaction is not committed nor rolled back and
subsequent inserts continue to be attempted from the same
transaction.
The problem might occur without the tablespace error if an
interrupt is received or an out of memory error occurs in a very
small window.
The INSPECT command with the BLOCKDATA option (similar to
INDEXDATA) performs block index to data consistency check and
detects if any rows are misplaced. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.2. *
**************************************************************** |
| Local Fix: |
Run INSPECT with the BLOCKDATA option to perform block index to
data consistency check. If a problem is detected, use LOAD from
cursor to insert into a copy of the MDC table to correct the
problem. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 version 10.1.0.2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.10.2012
07.12.2012
07.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
