DB2 - Problem description
Problem IC73725 | Status: Closed |
IN RARE CASE DB2 CAN TRAP IN SQLJPARSEDSC IF PROCESSING FDODSC IS INTERRUPTED BY A COMMUNICATION ERROR. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In rare case DB2 can trap in sqljParseDsc if processing FDODSC is interrupted by a communication error. Callstack: 0x0000002A969B9FA9 _Z12sqljParseDscP7sqljDsc + 0x0351 0x0000002A969FB2B9 _Z16sqljsParseSqldtaP13sqljsDrdaAsCbP14db2UCinterfaceP13sqljDDMO bject + 0x0151 0x0000002A969F01F1 _Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject + 0x03c1 0x0000002A969E02C2 _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U Cinterface + 0x007e 0x0000002A969E0971 _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x030d 0x0000002A969DE39F address: 0x0000002A969DE39F ; dladdress: 0x0000002A95782000 ; offset in lib: 0x000000000125C39F ; // libdb2e.so.1 0x0000002A969DE102 address: 0x0000002A969DE102 ; dladdress: 0x0000002A95782000 ; offset in lib: 0x000000000125C102 ; // libdb2e.so.1 0x0000002A969DBF21 address: 0x0000002A969DBF21 ; dladdress: 0x0000002A95782000 ; offset in lib: 0x0000000001259F21 ; // libdb2e.so.1 0x0000002A969DBD0C _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0x011e 0x0000002A969426DC _ZN8sqeAgent6RunEDUEv + 0x00c2 0x0000002A96E4E431 _ZN9sqzEDUObj9EDUDriverEv + 0x006d 0x0000002A96E4E3C1 _Z10sqlzRunEDUPcj + 0x0009 0x0000002A96C34AD6 sqloEDUEntry + 0x02ea db2diag.log errors: 2010-11-23-14.04.05.328213-300 E27509136E588 LEVEL: Error PID : 11318 TID : 186084485472 PROC : db2sysc 1 INSTANCE: abcde020 NODE : 001 DB : ABC APPHDL : 1-6785 APPID: AUTHID : XYZ EDUID : 50573 EDUNAME: db2agent (ABC) 1 FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:10 MESSAGE : DIA5000C A DRDA AS token "AGENT TERMINATING" was detected. The diagnostic data returned is (SRVDGN): "SQLERRP:SQLJCMN SQLCODE:-30081". 2010-11-23-14.04.05.359933-300 E27509725E867 LEVEL: Error PID : 11318 TID : 186084485472 PROC : db2sysc 1 INSTANCE: abcde020 NODE : 001 DB : ABC APPHDL : 1-6785 APPID: AUTHID : XYZ EDUID : 50573 EDUNAME: db2agent (ABC) 1 FUNCTION: DB2 UDB, DRDA Application Server, sqljsTermAgentReply, probe:11 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30081 sqlerrml: 27 sqlerrmc: * * 0 TCP/IP SOCKETS recv sqlerrp : SQLJCMN sqlerrd : (1) 0x81360012 (2) 0x00000012 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000001 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2010-11-23-14.04.35.081099-300 I27510593E568 LEVEL: Error PID : 11318 TID : 186298394976 PROC : db2sysc 1 INSTANCE: abcde020 NODE : 001 DB : ABC APPHDL : 1-7131 APPID: AUTHID : XYZ EDUID : 297774 EDUNAME: db2agent (ABC) 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 0x0000002B6000FA32 : 0100 | |
Problem Summary: | |
Users affected: All Problem summary: Trap in sqljParseDsc | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
First fixed in v9.7fp4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.01.2011 29.04.2011 29.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |