DB2 - Problem description
Problem IT29629 | Status: Closed |
APPLICATION CAN GET CAUGHT IN ENDLESS LOOP IN BSORTINITCNTSRTSTACKINFO IF APPLHEAPSZ = 2147483647 | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
When running SQL we can get caught in an endless loop in bsortInitCntSrtStackInfo if APPLHEAPSZ = 2147483647. The EDU stack can look like the following: Stack: ====================== 0x090000004090BE00 bsortInitCntSrtStackInfo__FP8sqeAgentP23SQLS_BSORT_CNTSRT_STACK + 0xA0 0x09000000408FEC3C sqlsBinSort__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTS + 0xC7C 0x09000000409019F0 sqlsBinSortIncremental__FP8sqeAgentP10SQLS_SLDESP10SQLS_SORTSi + 0x410 0x09000000408D9AC8 sqlsopen__FP8sqeAgentiT2P10SQLD_DPREDT2PP8SQLD_CCBPcPUcP12sqlri_ vectorPP10SQLD_VALUE + 0x3748 0x090000004078D818 IPRA.$sqldInsertTQ__FP8sqeAgentPcPP10SQLD_VALUET3P15SQLI_SUBAGNT _CB + 0x118 0x090000004078BFDC sqldParScanSort__FP8sqeAgent + 0x9DC 0x0900000040C3E7FC IPRA.$sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x159C 0x0900000040C37AB8 sqleProcessSubRequest__FP8sqeAgent + 0x2C38 0x090000003C12C8AC RunEDU__8sqeAgentFv + 0x9EC 0x090000003C106C40 EDUDriver__9sqzEDUObjFv + 0x300 0x090000003BFE8280 sqloEDUEntry + 0x360 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher * **************************************************************** | |
Local Fix: | |
Look to reduce the APPLHEAPSZ value below the maximum value(2147483647) eg. db2 update db cfg for SAMPLE using APPLHEAPSZ 10000 AUTOMATIC This should be done before you hit this issue. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.07.2019 20.01.2020 20.01.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |