suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT23202 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem 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. 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               * 
****************************************************************
Local Fix:
Specify explicitly INDEXING MODE INCREMENTAL in the LOAD command
available fix packs:
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

Solution
First fixed in Db2 11.1 Mod 3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2017
19.03.2018
19.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)