DB2 - Problem description
Problem IT21261 | Status: Closed |
DB2 MAY ABEND WHEN PLANS WITH SMP SORTS ARE INTERRUPTED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
The following db2diag.log message indicates this issue: 2017-05-11-11.39.34.195951+120 I647545A1192 LEVEL: Error PID : 6553686 TID : 68140 PROC : db2sysc 0 INSTANCE: db2jkl NODE : 000 DB : JKL APPHDL : 0-116 APPID: 10.0.0.1.32939.170505131326 AUTHID : SAPJKL HOSTNAME: hostname EDUID : 68140 EDUNAME: db2agnts (JKL) 0 FUNCTION: DB2 UDB, sort/list services, sqlsFetchNextTempRecord, probe:504 MESSAGE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER * DETECTED" DIA8003C The interrupt has been received. DATA #1 : Codepath, 8 bytes 8 DATA #2 : ZRC, PD_TYPE_ZRC, 4 bytes 0x80040003 DATA #3 : SQLS_MBUFS, PD_TYPE_SQLS_MBUFS, 1720 bytes SQLS_MBUFS: Address:a0002096bc1d0f8, Size:x6b8, Size:1720 x0688 pValues a0002096bc77b58 x0690 recptr a0002096bc771a0 x06AC records 1 x0698 recordBuffer a0002096bc771a0 x06A0 iNumBufferedRecords 0 x06A8 mergeFlags x00000002 - SQLS_CALLED_FETCH_NEXT_TEMP_REC x06B0 sortNum 0 x06B4 bufferedFetchRC -2147221501 2017-05-11-11.40.17.518767+120 I650353A3241 LEVEL: Severe PID : 6553686 TID : 68397 PROC : db2sysc 0 INSTANCE: db2jkl NODE : 000 DB : JKL APPHDL : 0-34142 APPID: 10.0.0.1.59560.170508132725 AUTHID : SAPJKL HOSTNAME: server EDUID : 68397 EDUNAME: db2agnts (JKL) 0 FUNCTION: DB2 UDB, sort/list services, sqlsSanityCheckPageAlreadyUnfixed, probe:4095 MESSAGE : ZRC=0x82130001=-2112684031=SQLS_NONSEVERE_PE "Sort List Services programming error." DIA8532C An internal processing error has occurred. DATA #1 : String, 83 bytes Sort Error. Failed sanity check before unfixing page, bpdPtr is null, aborting sort DATA #2 : Fix control block, PD_TYPE_SQLB_FIX_CB, 208 bytes accessMethod: SQLB_POOL_RELATIVE fixMode: 2 SQLBOLD buffptr: 0x0000000000000000 bpdPtr: 0x0000000000000000 pageLsnOnXLatch: 0000000000000000 dmDebugHdl: 0 objectPageNum: 2 empDiskPageNum: 4294967295 unfixFlags: 2000008 SQLB_UFIX_PURGE_MODE dirtyState: SQLBCLEAN fixInfoFlags: 0 regEDUid: 0 Pagekey: {pool:3;obj:2;type:128} PPNum:2 Obj: {pool:3;obj:2;type:128} Parent={3;2} lifeLSN: 0511114017040371 tid: 0 0 0 extentAnchor: 0 initEmpPages: 0 poolPage0: 0 poolflags: 0x 1111 objectState: 0x 80027 lastSMP: 0 pageSize: 16384 extentSize: 2 bufferPoolID: 1 partialHash: 2147614723 objDescAttributes: 0 objDescEHLState: 0x0000000000000000 bufferPool: 0x0a0002000d1f1a40 pdef: 0x0a0002000eae1e20 glob: 0x0000000117e95080 DATA #3 : Dumped object of size 3760 bytes at offset 0, 43 bytes /db2/P20/db2dump/6553686.68397.000.dump.bin CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x090000000FD5807C sqlsmergerec__FP8sqeAgentP10SQLS_SLDESP10SQLS_MBUFSUl + 0x19A8 [1] 0x090000000FD3DA00 sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL Z_RIDPc@OL@23903 + 0x434 [2] 0x09000000126DDDBC sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL Z_RIDPc + 0xA4 [3] 0x0900000012C6BEF4 sqlriFetch__FP8sqlrr_cbP9sqlri_taol + 0x138 [4] 0x0900000012C6BFC4 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x1C [5] 0x0900000012C6C01C sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x74 [6] 0x09000000115B7318 sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x5300 [7] 0x090000001153EA78 sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xDA0 [8] 0x090000001153F41C @82@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x230 [9] 0x09000000137ED784 RunEDU__8sqeAgentFv + 0x31EF4 [10] 0x09000000137749F0 RunEDU__8sqeAgentFv + 0x124 [11] 0x09000000124B3B9C EDUDriver__9sqzEDUObjFv + 0x134 [12] 0x0900000013766B80 sqloEDUEntry + 0x390 [13] 0x090000000053FE10 _pthread_body + 0xF0 [14] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF This is timing issue between two agents. Since this happens when a temp object is accessed the impact should be low and the query retried. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 M3 FP3. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
See Problem Description above. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.06.2017 16.03.2018 20.03.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |