DB2 - Problem description
Problem IT10280 | Status: Closed |
DB2 MIGHT ABORT WITH SIGSEGV IN SQLRIPERKEY2 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
DB2 might encounter a crash (SIGSEGV) in function sqlriPerKey2 if the DB2 registry varaible DB2_TCG_DEFAULT_OPTIONS="set multiple_pushdown off" is set. A typical stack trace might look like: <StackTrace> -------Frame------ ------Function + Offset------ 0x0900000009E8D81C sqlriPerKey2__FP8sqlrr_cb + 0x208 0x090000000A62824C sqldEvalDataPred__FP13SQLD_DFM_WORKPUlP10SQLD_DPRED + 0x3A8 0x09000000062F8EA4 sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL Z_RIDPc@OL@23691 + 0x328 0x090000000A340D00 sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL Z_RIDPc + 0xA4 0x090000000A2A5E94 sqlriFetch__FP8sqlrr_cbP9sqlri_taol + 0x11C 0x090000000A2A5F84 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x4C 0x090000000A2A5FDC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0xA4 0x090000000B6B35E4 sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0x4E38 0x090000000B716B2C sqlrr_subagent_router__FP8sqeAgentP12SQLE_DB2RA_T + 0xDF8 0x090000000B719D10 @81@sqleSubRequestRouter__FP8sqeAgentPUiPUl + 0x234 0x09000000096334C8 RunEDU__8sqeAgentFv + 0x2FB54 0x09000000095CA240 RunEDU__8sqeAgentFv + 0x124 0x090000000AAE4DFC EDUDriver__9sqzEDUObjFv + 0x130 0x0900000009B55664 sqloEDUEntry + 0x390 </StackTrace> | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 7. * **************************************************************** | |
Local Fix: | |
unset DB2_TCG_DEFAULT_OPTIONS | |
Solution | |
First fixed in DB2 Version 10.5 Fix Pack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.07.2015 21.01.2016 21.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |