DB2 FOR LUW / DB2FORLUW / 970 - DB2

This APAR fixes the following two related problems: 
 
1a. The first problem occurs after loading data into a table 
with constraints and then attaching that table to a partitioned 
table before using the SET INTEGRITY statement on the 
stand-alone table to validate the newly loaded data.  All rows 
from the newly attached partition should be visible after 
running the SET INTEGRITY statement on the partitioned table. 
However, the newly loaded rows are not visible when using an 
index scan. For this problem to occur, there must be one or more 
partitioned indexes on the range-partitioned table. In addition, 
the source table to be attached must have a matching index for 
each partitioned index on the target range-partitioned table. 
 
1b.  Furthermore, if a newly partitioned index is created before 
running the SET INTEGRITY statement on the partitioned table, 
then the loaded keys will, incorrectly not be included in the 
new index of the newly attached partition. This is a problem 
regardless of whether or not the partitioned indexes exist on 
the range-partitioned table prior to being attached. 
 
2.  The second problem occurs after loading data into a 
partitioned table with constraints and not running the SET 
INTEGRITY statement while detaching one of the partitions 
afterwards.  All rows from the detached partition (that is, the 
newly created stand-alone table) should be visible. However, the 
newly loaded rows are not visible when using an index scan.

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

To make the loaded data visible, the user can take ONE of the 
following actions: 
- load data into the problem partition 
- execute the REORG INDEXES ALL command 
 
In order to fix the corrupted index problem mentioned in 1b, the 
user must execute the REORG INDEXES ALL command.

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

The problem is first fixed in DB2 version 9.7.0.6.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC83469 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.04.2012
04.06.2012
06.06.2012

9.7.0.6