IT23202: LOAD OF BITEMPORAL TABLES MIGHT FAIL TO DETECT DUPLICATE / OVERLAPPING ROWS WITH INDEXING MODE REBUILD

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• A LOAD of bitemporal tables might fail to detect duplicate /
  overlapping rows with INDEXING MODE REBUILD.
  
  A table may already contain existing rows. In some special
  scenarios it can occur that during subsequent LOAD there are
  more than just one rows loaded that are violating the
  overlapping business time constraint. These rows are not
  detected by LOAD and end up with an corrupted index.
  
  Running a db2dart against the table might show errors like this:
  
       Index inspection phase start. Index obj: 133  In pool: 234
         Scanning pages for unique index itoken(0) root page:1p.
         Scanning pages for unique index itoken(1) root page:2p.
           Error: Overlap with previous key in unique BTWO index.
  Lvl(1) Page,slot,rid current:8397p,889,x0000000000B80016
  prev:13p,888,x0000000045370027.
           Error: Overlap with previous key in unique BTWO index.
  Lvl(1) Page,slot,rid current:8411p,740,x00000000019D0029
  prev:27p,739,x0000000045CF0022.
           Error: Overlap with previous key in unique BTWO index.
  Lvl(1) Page,slot,rid current:50469p,1004,x00000000020A000B
  prev:37p,1003,x00000000020A000B.
  ...
  

Local fix

• Specify explicitly INDEXING MODE INCREMENTAL in the LOAD command
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1 Mod 3 Fix Pack 3
  

Temporary fix

Comments

APAR Information

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

• 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

• RB10 PSN

     UP