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 IC63977 Status: Closed

IN RARE TIMING SITUATIONS, SORT WITH INTRA_PARALLEL MAY FAIL WITH -901
CREATING TEMPORARY TABLE FOR SORT SPILL.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When the INTRA_PARALLEL db cfg parameter is enabled (smp 
parallelism),  an operation requiring Sort infrastructure that 
spills to a temp table may fail with a -901 with a db2diag.log 
entry like this: 
 
FUNCTION: DB2 UDB, sort/list services, sqlsmergerec, probe:2050 
MESSAGE : Creating Temporary Table for sort spill, but one 
already exists. 
          Aborting sort operation. Contact IBM Support. 
slestatus = 874c40, 
          poolID = 5, objectID = 73 
 
This is caused by a rare timing scenario and is unlikely to 
occur.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When the INTRA_PARALLEL db cfg parameter is enabled (smp     * 
* parallelism),  an operation requiring Sort infrastructure    * 
* that spills to a temp table may fail with a -901 with a      * 
* db2diag.log entry like this:                                 * 
*                                                              * 
* FUNCTION: DB2 UDB, sort/list services, sqlsmergerec,         * 
* probe:2050                                                   * 
* MESSAGE : Creating Temporary Table for sort spill, but one   * 
* already exists.                                              * 
*           Aborting sort operation. Contact IBM Support.      * 
* slestatus = 874c40,                                          * 
*           poolID = 5, objectID = 73                          * 
*                                                              * 
* This is caused by a rare timing scenario and is unlikely to  * 
* occur.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Workaround: disable INTRA_PARALLEL db config parameter       * 
****************************************************************
Local Fix:
turn off INTRA_PARALLEL, i.e. change dbm cfg parameter 
INTRA_PARALLEL to NO then recycle the instance
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed in v97fp1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
23.02.2010
23.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList