DB2 FOR LUW / DB2FORLUW / A50 - DB2

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.

**************************************************************** 
* 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.              * 
****************************************************************

Please refrain from using increment sort memory by: 
db2set DB2_INCREMENTAL_SORT_MEMORY=OFF 
db2stop 
db2start

This problem was first fixed in DB2 V10.5 FixPack 5.

keiner bekannt / siehe Local-Fix

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

05.06.2014
13.03.2015
13.03.2015