IC87500: ROWS MIGHT BE INSERTED INTO WRONG MDC TABLE CELL AFTER PREVIOUS INSERTS IN SAME TRANSACTION ENCOUNTER TABLESPACE FULL

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

APAR status

• Closed as program error.

Error 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.
  

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.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 version 10.1.0.2.                             *
  ****************************************************************
  

Problem conclusion

• The problem is first fixed in DB2 version 10.1.0.2.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IC87345

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RA10 PSN

     UP