|
Problem IC71545
|
Status: Closed |
DBARTISAN CAUSE SIGNAL 11 WITH DB2 INSTANCE TO CRASH ON THE DATABASE SIDE WHEN CALLING STORED PROCEDURE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
While using dbArtisan to run a stored procedure cause the DB2
instance to crash on the database side, with signal 11:
Signal # 11 in function sdbg_GetRep() when a store procedure was
running.
2009-10-30-14.01.54.700512-240 E9816642E838 LEVEL:
Critical
PID : 15177 TID : 186566830432 PROC :
db2sysc 8
INSTANCE: db2insts1 NODE : 008
EDUID : 88524 EDUNAME: db2agntdp (ADMIN ) 8
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "Panic". The instance may have been shutdown as a
result.
"Automatic" FODC (First Occurrence Data Capture) has been
invoked and
diagnostic information has been recorded in directory
"/var/ibmdb2/db2insts1/sqllib/db2dump/FODC_Trap_2009-10-30-14.01
.38.81
2534/". Please look in this directory for detailed
evidence about
what happened and contact IBM support if necessary to
diagnose the
problem.
15153.301065.001.trap.txt:
<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet
href="http://raspd.torolab.ibm.com/db2trapfile.xsl"
type="text/xsl"?>
<DB2TrapFile version="1.0">
<Trap>
<Header>
DB2 build information: DB2 v9.5.0.4 timestamp:
2009-10-30-14.01.38.828019 instance name: db2insts1.001
EDU name : db2agent (WISEDB) 1
EDU ID : 301065
Signal #11
uname: S:Linux R:2.6.9-68.9.ELmsdw.2smp V:#1 SMP Fri Jan 16
14:43:40
EST 2009 M:x86_64 N:pi600c3n4
process id: 15153
thread id : 183119112544 (0x2AA2BFE960)
</Header>
<StackTrace>
---FUNC-ADDR---- ------FUNCTION + OFFSET------
0000002A9B7C91AF ossDumpStackTraceEx + 0x01f7
(/ds/9.5.4.7/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2osse.s
o.1)
0000002A9B7C4CEA _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00b4
(/ms/dist/ibmdb2/PROJ/ds/9.5.4.7/.exec/x86_64.linux.2.6.glibc.2.
3/lib64/libdb2osse.so.1)
0000002A9B7C4DB1 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009
(/ds/9.5.4.7/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2osse.s
o.1)
This issue has been fixed in the newest version of dbArtisan,
however we have added defence code to bring down DB2 with out
causing a signal 11. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DBARTISAN CAUSE SIGNAL 11 WITH DB2 INSTANCE TO CRASH ON THE *
* DATABASE SIDE WHEN CALLING STORED PROCEDURE. *
****************************************************************
* PROBLEM DESCRIPTION: *
* While using dbArtisan to run a stored procedure cause the *
* DB2 *
* instance to crash on the database side, with signal 11: *
* *
* *
* *
* Signal # 11 in function sdbg_GetRep() when a store procedure *
* was *
* running. *
* *
* *
* *
* *
* 2009-10-30-14.01.54.700512-240 E9816642E838 LEVEL: *
* *
* Critical *
* *
* PID : 15177 TID : 186566830432 PROC : *
* *
* db2sysc 8 *
* *
* INSTANCE: db2insts1 NODE : 008 *
* *
* EDUID : 88524 EDUNAME: db2agntdp (ADMIN ) *
* 8 *
* FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10 *
* *
* MESSAGE : ADM14001C An unexpected and critical error has *
* *
* occurred: "Panic". The instance may have been shutdown as a *
* result. *
* "Automatic" FODC (First Occurrence Data Capture) has been *
* invoked and *
* diagnostic information has been recorded in directory *
* *
* "/var/ibmdb2/db2insts1/sqllib/db2dump/FODC_Trap_2009-10-30-14.
* *
* 2534/". Please look in this directory for detailed *
* evidence about *
* *
* what happened and contact IBM support if necessary *
* to diagnose the *
* *
* problem. *
* *
* 15153.301065.001.trap.txt: *
* *
* <?xml version="1.0" encoding="ISO-8859-1"?> *
* *
* <?xml-stylesheet *
* *
* href="http://raspd.torolab.ibm.com/db2trapfile.xsl" *
* *
* type="text/xsl"?> *
* *
* <DB2TrapFile version="1.0"> *
* *
* <Trap> *
* *
* <Header> *
* *
* DB2 build information: DB2 v9.5.0.4 timestamp: *
* 2009-10-30-14.01.38.828019 instance name: db2insts1.001 *
* EDU name : db2agent (WISEDB) 1 *
* *
* EDU ID : 301065 *
* *
* *
* Signal #11 *
* *
* *
* uname: S:Linux R:2.6.9-68.9.ELmsdw.2smp V:#1 SMP Fri Jan 16 *
* *
* 14:43:40 *
* *
* EST 2009 M:x86_64 N:pi600c3n4 *
* *
* process id: 15153 *
* *
* *
* thread id : 183119112544 (0x2AA2BFE960) *
* *
* *
* </Header> *
* *
* *
* <StackTrace> *
* *
* *
* ---FUNC-ADDR---- ------FUNCTION + OFFSET------ *
* *
* *
* 0000002A9B7C91AF ossDumpStackTraceEx + 0x01f7 *
* *
* *
* (/ds/9.5.4.7/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2osse
* *
* *
* 0000002A9B7C4CEA _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + *
* 0x00b4 *
* *
* (/ms/dist/ibmdb2/PROJ/ds/9.5.4.7/.exec/x86_64.linux.2.6.glibc.
* *
* 0000002A9B7C4DB1 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + *
* 0x0009 *
* (/ds/9.5.4.7/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2osse
* *
* This issue has been fixed in the newest version of *
* dbArtisan, however we have added defence code to bring down *
* DB2 with out causing a signal 11. *
****************************************************************
* RECOMMENDATION: *
* First fixed in fix pack 8 of v9.5 *
**************************************************************** |
| Local Fix: |
Please upgrade your dbArtisan to the newest available version.
This problem has not been seen in IBM Data Studio or Optim
Development Studio. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in fix pack 8 of v9.5 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC75475
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.09.2010
13.07.2011
13.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
