|
Problem IT02237
|
Status: Closed |
SORT MIGHT TRAP AT BSORTGETFIRSTPARTIALKEY DUE TO INCORRECT INCREMENTAL SORT MEMORY. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
An SQL statement involves sort operation might cause various
symptom like as follows.
a) SEGV or Access Violation with stack like below:
a-1)
sqlsBinSortPopulateRecPointers
bsortGetFirstPartialKey
sqlsBinSort
sqlswrit
sqlsBinSortIncremental
a-2)
bsortGetFirstPartialKey
sqlsBinSort
sqlswrit
sqlsBinSortIncremental
b) Bad page on a temp table with stack like below:
sqldFetchDirect
mergfetc
sqlsopen
sqlrsopen
sqlrisrt
This problem is likely to happen if the width of the table or
result set to be sorted can exceed 64K byte.
The current minimum block siz is 64K, and this is not right
because it isn't big enough to store a maximum sized record. The
fix is to change the minimum block size to at least as big as
the maximum size of record. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who sort row width of the table or *
* result set to be sorted can exceed 64K byte. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V10.5 FixPack 5 or later. *
**************************************************************** |
| Local Fix: |
Please refrain from using increment sort memory by:
db2set DB2_INCREMENTAL_SORT_MEMORY=OFF
db2stop
db2start |
| Solution |
This problem was first fixed in DB2 V10.5 FixPack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.06.2014
13.03.2015
13.03.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
