DB2 - Problem description
Problem IC87345 | 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 / 970 - 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 9.7.0.8. * **************************************************************** | |
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 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 version 9.7.0.8. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC87497 IC87498 IC87500 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.10.2012 25.03.2013 26.03.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.0.8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |