DB2 FOR LUW / DB2FORLUW / A50 - DB2

An index scan on a data partitioned table may trap or return in 
correct results if there were no available partitions when the 
scan was started, but a partition becomes visible (via a SET 
INTEGRITY command) before the scan completes. 
 
If there are no visible partitions when a partitioned index scan 
is started, the scan is expected to return no rows on fetch. 
Due to an error, if a data partition becomes visible during the 
scan, 
 we will attempt to retrieve data and the wrong rows may be 
returned, predicates may be ignored, data rows may be returned 
out of order, or other unexpected errors may occur. 
 
If the index scan is using an index on expression, the attempt 
to retrieve data may trap.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of data partitioned tables                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 FixPack 7.                           * 
****************************************************************

Run SET INTEGRITY on newly attached partitions before detaching 
the last existing partition, or run SET INTEGRITY with the ALLOW 
NO ACCESS option.

Problem is first fixed in DB2 UDB version 10.5 fix pack 7.

keiner bekannt / siehe Local-Fix

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

25.05.2015
19.01.2016
29.04.2016