Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC71276 Status: Closed

AN OPERATION REQUIRING A SORT THAT EXPERIENCES INSUFFICIENT MEMORY SCENARIO
MAY TRAP.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
When Sort is using INCREMENTAL memory allocation (this is 
default for most sorts), and sort is not able to allocate enough 
memory for binsort structures to perform binsort on all records 
that were cached before spilling, then sort will perform the 
binsort on smaller chunks of records. In this scenario, sort 
will also check if each of the sorted chunks is already is 
sorted order. The method used to perform this check may cause a 
trap. 
We believe the problem is not pervasive. 
Symptom of this trap may differ slightly at the top of the 
stack, but will always contain 
sqlsBinSortIncremental()->sqlsCheckFSEQAcrossSpills()->sqlsInser 
tCompare(). 
 
  sqlv_bin_ncmp 
  sqlsInsertCompare 
  sqlsCheckFSEQAcrossSpills 
  sqlsBinSortIncremental 
  sqlsBuildRow 
  sqlsinsr 
  sqldReorgSortRow 
  sqldEvalDataPred 
  sqldReadNorm 
  sqldFetchNext 
  sqldFetchNext 
  sqldfrd 
  sqldReorgTableScanSort
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When Sort is using INCREMENTAL memory allocation (this is    * 
*                                                              * 
* default for most sorts), and sort is not able to allocate    * 
* enough                                                       * 
* memory for binsort structures to perform binsort on all      * 
* records                                                      * 
* that were cached before spilling, then sort will perform the * 
*                                                              * 
* binsort on smaller chunks of records. In this scenario, sort * 
*                                                              * 
* will also check if each of the sorted chunks is already is   * 
*                                                              * 
* sorted order. The method used to perform this check may      * 
* cause a                                                      * 
* trap.                                                        * 
*                                                              * 
* We believe the problem is not pervasive.                     * 
*                                                              * 
* Symptom of this trap may differ slightly at the top of the   * 
*                                                              * 
* stack, but will always contain                               * 
*                                                              * 
* sqlsBinSortIncremental()->sqlsCheckFSEQAcrossSpills()->sqlsIns 
* tCompare().                                                  * 
*                                                              * 
*                                                              * 
*                                                              * 
*   sqlv_bin_ncmp                                              * 
*                                                              * 
*   sqlsInsertCompare                                          * 
*                                                              * 
*   sqlsCheckFSEQAcrossSpills                                  * 
*                                                              * 
*   sqlsBinSortIncremental                                     * 
*                                                              * 
*   sqlsBuildRow                                               * 
*                                                              * 
*   sqlsinsr                                                   * 
*                                                              * 
*   sqldReorgSortRow                                           * 
*                                                              * 
*   sqldEvalDataPred                                           * 
*                                                              * 
*   sqldReadNorm                                               * 
*                                                              * 
*   sqldFetchNext                                              * 
*                                                              * 
*   sqldFetchNext                                              * 
*                                                              * 
*   sqldfrd                                                    * 
*                                                              * 
*   sqldReorgTableScanSort                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.1 FP10                                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
First fixed in V9.1 FP10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.09.2010
10.06.2011
10.06.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.