|
Problem IC98683
|
Status: Closed |
ROWS MISSING WHEN LARGE RESULT SET IS PRODUCED BY NULLS FIRST SORT ON INTEGER OR BIGINT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If sort is done with DESC (NULLS FIRST) on INT or BIGINT data
types and the result set is large, then it is possible that the
query does not return part of the rows back to the user. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.4. *
**************************************************************** |
| Local Fix: |
Do not use sort with DESC (NULLS FIRST) on INT or BIGINT data
types. Or, if you must use such a sort, then use the following:
db2set DB2_TCG_DEFAULT_OPTIONS="set num_page_fast_int_sort 0"
Then recycle the instance using db2stop followed by db2start and
recompile any static sections that use sort with DESC (NULLS
FIRST) on INT or BIGINT data types. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 version 10.1.0.4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.01.2014
18.07.2014
18.07.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
