DB2 - Problem description
Problem IC95592 | Status: Closed |
TRAP IN SQLODSHR CALLED FROM SQLESUBCOORDTERM | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Partition one trapped db2diag.log reported multiple SQLO_NOMEM_DBH errors for threads db2agntp, db2lrid, db2lload, db2lbm15, and right after the first time SQLO_NOMEM_DBH reported by db2agnsc, db2agnsc trapped with SIGSEGV: 2013-02-28-12.33.45.177465-360 I935506964E665 LEVEL: Severe PID : 33009 TID : 46921645287168 PROC : db2sysc 19 INSTANCE: db2admn NODE : 019 DB : FDW2D APPHDL : 901-52060 APPID: *N901.db2admn.130228182524 AUTHID : BEATADMN HOSTNAME: br95db05 EDUID : 391137 EDUNAME: db2lrid 19 FUNCTION: DB2 UDB, data management, sqldDictBuilder, probe:10 MESSAGE : ZRC=0x8B0F0002=-1961951230=SQLO_NOMEM_DBH "No memory available in 'Database Heap'" DIA8302C No memory available in the database heap. DATA #1 : String, 41 bytes Out of memory in dictionary builder class ... 2013-03-04-20.05.07.069124-360 I1165392843E597 LEVEL: Severe PID : 58331 TID : 46923104904960 PROC : db2sysc 1 INSTANCE: db2admn NODE : 001 DB : FDW2D APPHDL : 0-4088 APPID: *N0.db2admn.130305020108 AUTHID : DB2ADMN HOSTNAME: br95db03 EDUID : 36335 EDUNAME: db2agnsc 1 FUNCTION: DB2 UDB, base sys utilities, sqleSubCoordInit, probe:20 RETCODE : ZRC=0x8B0F0002=-1961951230=SQLO_NOMEM_DBH "No memory available in 'Database Heap'" DIA8302C No memory available in the database heap. The trapping EDUID 36336 did report those errors prior to the trap: 2013-03-04-20.05.06.961903-360 E1165385051E600 LEVEL: Error PID : 58331 TID : 46924883289856 PROC : db2sysc 1 INSTANCE: db2admn NODE : 001 DB : FDW2D APPHDL : 0-4088 APPID: *N0.db2admn.130305020108 AUTHID : DB2ADMN HOSTNAME: br95db03 EDUID : 36336 EDUNAME: db2agnsc 1 FUNCTION: DB2 UDB, data protection services, sqlpInitAgent, probe:400 MESSAGE : ZRC=0x8B0F0002=-1961951230=SQLO_NOMEM_DBH "No memory available in 'Database Heap'" DIA8302C No memory available in the database heap. 2013-03-04-20.05.07.000201-360 I1165385652E597 LEVEL: Severe PID : 58331 TID : 46924883289856 PROC : db2sysc 1 INSTANCE: db2admn NODE : 001 DB : FDW2D APPHDL : 0-4088 APPID: *N0.db2admn.130305020108 AUTHID : DB2ADMN HOSTNAME: br95db03 EDUID : 36336 EDUNAME: db2agnsc 1 FUNCTION: DB2 UDB, base sys utilities, sqleSubCoordInit, probe:20 RETCODE : ZRC=0x8B0F0002=-1961951230=SQLO_NOMEM_DBH "No memory available in 'Database Heap'" DIA8302C No memory available in the database heap. 2013-03-04-20.05.07.408839-360 I1165409421E589 LEVEL: Error PID : 58331 TID : 46924883289856 PROC : db2sysc 1 INSTANCE: db2admn NODE : 001 DB : FDW2D APPHDL : 0-4088 APPID: *N0.db2admn.130305020108 AUTHID : DB2ADMN HOSTNAME: br95db03 EDUID : 36336 EDUNAME: db2agnsc 1 FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:1 MESSAGE : Error in agent servicing application with coor_node: DATA #1 : Hexdump, 2 bytes 0x00002AAD8C00F952 : 0000 ... db2agnsc (EDUID 36336) trapped with the following stacks: 0x00002AAAB2315D2A _Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 0x020a 0x00002AAAB2315ABB ossDumpStackTraceV98 + 0x002b 0x00002AAAB23109E3 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvmm + 0x0103 0x00002AAAADE5C327 sqlo_trce + 0x0407 0x00002AAAADEA7517 sqloEDUCodeTrapHandler + 0x0277 0x000000387DC0F500 __PRETTY_FUNCTION__.6770 + 0x0040 0x00002AAAAC73A01C sqlodshr + 0x005c 0x00002AAAAD469DE2 _Z16sqleSubCoordTermP8sqeAgentP5sqlcai + 0x0382 0x00002AAAAD46A218 _Z26sqleSubCoordProcessRequestP8sqeAgent + 0x00a8 0x00002AAAABCEAE83 _ZN8sqeAgent6RunEDUEv + 0x0683 0x00002AAAACCD0213 _ZN9sqzEDUObj9EDUDriverEv + 0x00f3 0x00002AAAACCD0119 _Z10sqlzRunEDUPcj + 0x0009 0x00002AAAAC75CFC1 sqloEDUEntry + 0x02a1 0x000000387DC07851 pthread_timedjoin_np + 0x0071 0x000000387D4E811D clone + 0x006d | |
Problem Summary: | |
TRAP IN SQLODSHR CALLED FROM SQLESUBCOORDTERM | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.08.2013 31.03.2014 31.03.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |