| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT03088 | Status: Closed |
DB2 CRASHES AT SQLSBINSORTPOPULATERECPOINTERS WHEN DOING RESETTABLE SORT | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Problem description: DB2 crashed in sqlsBinSortPopulateRecPointers() and may lead to memory corruption in other fuctions. A possible stack trace is: <StackTrace> -------Frame------ ------Function + Offset------ 0x0900000019F39A7C @114@sqlsBinSortPopulateRecPointers__FP10SQLS_SLDESP10SQLS_SORTS PUcPUiiN25PUlCP24SQLS_BSORT_ICUBUFFER_ROWP8sqeAgent + 0x340 0x0900000019537F80 bsortGetFirstPartialKey__FP8sqeAgentPUcPUiP10SQLS_SLDESP10SQLS_S ORTSiUiT3PiPUl + 0xADC 0x0900000019536248 sqlsBinSort__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTS + 0x890 0x090000001C41E078 sqlswrit__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTSi + 0x7E8 0x0900000019241A94 sqlsBinSortIncremental__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTSi + 0x31C 0x09000000192DF608 .@114@sqlsBuildRow.fdpr.clone.4536__FP8sqeAgentP10SQLS_SLDESP10S QLS_SORTSPibP7OSSTickP12OSSTickDeltaPP10SQLD_VALUE + 0x66C 0x09000000192DF9D8 .sqlsinsr.fdpr.clone.289__FP8sqeAgentPcPUcP12sqlri_vectorPP10SQL D_VALUE + 0x324 0x09000000192DFE9C sqlrsinsr__FP8sqlrr_cbP10sqlri_iudo + 0x78 0x09000000192E00CC sqlrisrt__FP8sqlrr_cb + 0x114 0x090000001AA5A734 sqlriMergeStream__FP8sqlrr_cb + 0x694 0x09000000192F1DC8 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x24 0x090000001910B868 sqlrr_process_fetch_request__FP14db2UCinterface + 0xF60 0x0900000019B439F8 sqlrr_open__FP14db2UCinterfaceP15db2UCCursorInfo + 0x17F0 0x090000001910A1CC sqljs_ddm_opnqry__FP14db2UCinterfaceP13sqljDDMObject + 0x1DD4 0x090000001926C5B8 sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC interface + 0x1C8 0x090000001926A774 .sqljsParse.fdpr.clone.102__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 sqeAgentb + 0x13A4 0x09000000192672B0 @73@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x280 0x09000000197FE564 @73@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xB4 0x09000000197FEF4C @73@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x4E8 0x09000000197FE230 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x21C 0x0900000018FBAC80 RunEDU__8sqeAgentFv + 0x584 0x0900000018FB6858 EDUDriver__9sqzEDUObjFv + 0x13C 0x0900000018FB66E0 sqlzRunEDU__FPcUi + 0x10 0x0900000018FC9558 sqloEDUEntry + 0x264 </StackTrace> The resettable sort always tries to allocate enough space for maxnodes instead of sliNumRecords. This is because the buffer is going to be re-used for subsequent sorts so we should grab as much memory as we are allowed to. If we hit a constrained memory issue, we could end up allocating less than that.. maybe 1/3 of maxnodes. Since it is only sorting sliNumRecords, it needs to recalculate the # of iterations. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 Fix Pack 5 or higher * **************************************************************** | |
| Local Fix: | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.07.2014 15.07.2015 16.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|
