DB2 - Problem description
Problem IC98556 | Status: Closed |
DB2FMP ABEND and SQL1131N ERROR IS OBSERVED DURING reorgchk_tb_stats(..) RUN WITH DB2MEMDBG=PROTECT | |
product: | |
DB2 CONNECT / DB2CONNCT / A50 - DB2 | |
Problem description: | |
On serial instance with DB2MEMDBG=PROTECT, After a few hours run, db2fmp started hitting abend (-1131) very frequently and one might see many "*.app_trap.txt" files generated under DIAGPATH. 2013-09-03-00.39.55.455965-240 I320178A2003 LEVEL: Event PID : 26607858 TID : 71404 PROC : db2sysc INSTANCE: svtdbm4 NODE : 000 DB : PROTEUS APPHDL : 0-28709 APPID: *LOCAL.svtdbm4.130903042941 AUTHID : SVTDBM4 HOSTNAME: **** EDUID : 71404 EDUNAME: db2agent (PROTEUS) FUNCTION: DB2 UDB, oper system services, sqlossig, probe:10 MESSAGE : Sending SIGKILL to the following process id DATA #1 : signed integer, 4 bytes 18808974 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x0900000009633288 pdLog + 0x248 [1] 0x090000000C2E6228 sqlossig + 0xA0 [2] 0x0900000008B12090 sqlerReturnFmpToPool__FcT1P14sqlerFmpHandleP8sqeAgent + 0x16B4 [3] 0x0900000009D448F4 sqlriInvokeInvoker__FP10sqlri_ufobb + 0x102C [4] 0x0900000009D46EA8 sqlriInvokeInvoker__FP10sqlri_ufobb + 0x870 [5] 0x0900000008AB9D30 sqlricall__FP8sqlrr_cb + 0x630 [6] 0x0900000009ED21AC sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x8E0 [7] 0x090000000A54ACA4 sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x1AA0 [8] 0x090000000A5496AC sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x4A8 [9] 0x090000000994F708 sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x30FC [10] 0x09000000099A6048 sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC interface + 0x16BC [11] 0x090000000A0A2764 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x22BC [12] 0x090000000A0A240C @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x1F64 [13] 0x090000000CA7A958 RunEDU__8sqeAgentFv + 0xB728 [14] 0x090000000CA78FDC RunEDU__8sqeAgentFv + 0x9DAC [15] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF [16] 0x090000000CA95820 RunEDU__8sqeAgentFv + 0x17C [17] 0x090000000904BE04 EDUDriver__9sqzEDUObjFv + 0x14C [18] 0x090000000C0695B8 sqloEDUEntry + 0x2DC [19] 0x0900000000790D50 _pthread_body + 0xF0 [20] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 2013-09-03-00.39.55.456793-240 I322182A1029 LEVEL: Error PID : 26607858 TID : 71404 PROC : db2sysc INSTANCE: svtdbm4 NODE : 000 DB : PROTEUS APPHDL : 0-28709 APPID: *LOCAL.svtdbm4.130903042941 AUTHID : SVTDBM4 HOSTNAME: **** EDUID : 71404 EDUNAME: db2agent (PROTEUS) FUNCTION: DB2 UDB, routine_infrastructure, sqlerInvokeFencedRoutine, probe:99 MESSAGE : ZRC=0xFFFFFB95=-1131 SQL1131N A stored procedure process has been terminated abnormally. Routine name: "". Specific name: "". DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1131 sqlerrml: 0 sqlerrmc: sqlerrp : SQLJCMN sqlerrd : (1) 0x8136001C (2) 0x0000001C (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: <SignalDetails> <Siginfo_t length="64"> 0000000B 00000000 00000033 00000000 00000000 00000000 07000000 001DDBF8 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 </Siginfo_t> Signal #11 (SIGSEGV): si_addr is 0x07000000001DDBF8, si_code is 0x00000033 (SEGV_ACCERR:Invalid permissions for mapped object.) </SignalDetails> <StackTrace> -------Frame------ ------Function + Offset------ 0x0900000003F3A6B8 csmCursorBlaster__FP14db2UCinterfaceUiT2PUiN22@OL@6534 + 0x7C 0x0900000003E3A928 csmCursorBlaster__FP14db2UCinterfaceUiT2PUiN22 + 0x398 0x0900000003E1924C sqlerFmpSendFini + 0x124 0x0900000003DFFB3C sqlerFmpListener + 0xDF8 0x0000000100001224 main + 0x944 </StackTrace> Sample Repro: db2set DB2MEMDBG=PROTECT db2stop db2start db2 connect to sample db2 "create table myschema.t1(c1 integer) " db2 "call sysproc.reorgchk_tb_stats('T', 'MYSCHEMA.T1') " SQL1131N A stored procedure process has been terminated abnormally. Routine name: "SYSPROC.REORGCHK_TB_STATS". Specific name: "REORGCHK_TB_STATS". SQLSTATE=38503 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * db2 connect users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2_v105fp3 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Problem fixed in and from db2_v105fp3 onwards | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.01.2014 08.09.2014 08.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |