DB2 FOR LUW / DB2FORLUW / A10 - DB2

Background Information: 
 
1) Table partitioning allows for the efficient roll-in and 
roll-out of table data. The ALTER TABLE statement with the 
ATTACH PARTITION clause makes data roll-in very easy. It takes 
an existing table (source table) and attaches it to the target 
table as a new data partition. The newly attached data partition 
is unavailable to queries initially after the attach statement 
is complete, while the rest of the table remains online after 
attach. SET INTEGRITY is required to perform range checking, 
constraint checking, and maintenance of the non-partitioned 
indexes before bringing the partition online. 
 
2)  Whenever you create an XML column, an XML path index is 
automatically created by the DB2 software on the XML column. 
The XML path index records all unique paths which exist within 
XML documents stored in an XML column. 
 
3) Certain database operations, such as a rollforward through a 
create index that was not fully logged, can cause an index 
object to become invalid. This is because the index is not 
created during the rollforward operation.  When the database 
manager detects that an index is no longer valid, it 
automatically attempts to rebuild it.  When the rebuild takes 
place, it is controlled by the indexrec parameter of the 
database or database manager configuration file. 
 
Problem Details: 
 
The XML path index on a range partitioned table might be rebuilt 
through the REORG command, or because it was previously marked 
invalid and DB2 has decided to rebuild it. If this occurs while 
there exists a partition that has been attached but not brought 
online using SET INTEGRITY, then the XML path index is rebuilt 
without including the paths from the newly attached partition. 
This can result in incorrect results when scanning an XML values 
index, if the newly attached partition contains paths that are 
not found in any of the other partitions.

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

Run SET INTEGRITY on the table and then rebuild the indexes 
with the REORG INDEXES command.

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
 

The problem is first fixed in DB2 version 10.1.0.3.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

24.01.2013
27.09.2013
27.09.2013