|
Problem IT09085
|
Status: Closed |
INDEX SCAN ON A DATA PARTITIONED TABLE MAY TRAP OR RETURN INCORRECT RESULTS IF PARTITIONS BECOME AVAILABLE DURING THE SCAN |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of data partitioned tables *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.5 FixPack 7. *
**************************************************************** |
| Local Fix: |
Run SET INTEGRITY on newly attached partitions before detaching
the last existing partition, or run SET INTEGRITY with the ALLOW
NO ACCESS option. |
| Solution |
Problem is first fixed in DB2 UDB version 10.5 fix pack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.05.2015
19.01.2016
29.04.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
