|
Problem IC94297
|
Status: Closed |
RANGE PARTITIONED TABLES DEFINED WITH A NULLS FIRST PARTITIONING COLUMN MIGHT RETURN UNORDERED DATA |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Queries using a range partitioned table defined with a NULLS
FIRST partitioning column, a partitioned index, and NULL values
in the data might return unordered data.
When the query contains no predicates on the column defined as
NULLS FIRST and specifies an ORDER BY clause containing the
columns of the partitioned index, then the NULL values are
interspersed with other data from the table instead of being
output at the end of the result set.
The partitioned index must be used in the access plan and the
access plan must not contain a SORT. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 LUW version 9.7 Fix Pack 9. *
**************************************************************** |
| Local Fix: |
Drop the relevant index or convert it a non-partitioned index or
change the sequence or direction of columns used in the ORDER BY
clause so that they do not exactly match to the index. |
| available fix packs: |
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
|
| Solution |
Problem was first fixed in DB2 LUW version 9.7 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.07.2013
17.12.2013
17.12.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.9
|
 |
| 9.7.0.9
|
|
