DB2 - Problembeschreibung
Problem IC83897 | Status: Geschlossen |
DB2 CONNECT GATEWAY INSTANCE MAY CRASH DUE TO MEMORY CORRUPTION AT SQLJRPROCESSSETI() | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / A10 - DB2 | |
Problembeschreibung: | |
DB2 Connect gateway may crash when a JCC application from DB2 Client sends incorrect CLIENT ACCTNG value with length more than 256 characters. <StackTrace> -----FUNC-ADDR---- ------FUNCTION + OFFSET------ 0x0000020004D1FE8E ossDumpStackTrace + 0x00d6 (/dbc/home/dbcsib01/sqllib/lib64/libdb2osse.so.1) 0x0000020004D1B67E _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00c2 (/dbc/home/dbcsib01/sqllib/lib64/libdb2osse.so.1) 0x0000020001F70486 sqlo_trce + 0x066e (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020002006364 sqloEDUCodeTrapHandler + 0x0134 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x000002001F409DF0 address: 0x2001f409df0 0x0000020001FD227E sqloCrashOnCriticalMemoryValidationFailure + 0x002e (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020001FE91FE _ZN13SQLO_MEM_POOL32diagnoseMemoryCorruptionAndCrashEmPKc + 0x01f6 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020001FE74D6 _ZN13SQLO_MEM_POOL10MemTreePutEP8SMemNodemP17SqloChunkSubgroup + 0x021e (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020001FD4FF6 sqlofmblkEx + 0x07aa (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x000002000118031A _Z16sqljrProcessSetiP14db2UCinterface13SQLJRSETITYPE + 0x023a (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x000002000117FF50 _Z19sqljrPreProcessSetiP14db2UCinterface + 0x0330 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x00000200011853B2 _Z18sqljrPreProcessSQLP13sqljrDrdaArCbP14db2UCinterface13sqljrRq stTypeb + 0x03aa (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020001154174 _Z20sqljrDrdaArExcSqlSetP14db2UCinterface + 0x0358 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x00000200011C0EA4 _Z19sqljs_ddm_excsqlsetP14db2UCinterfaceP13sqljDDMObject + 0x1540 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020001196F76 _Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U Cinterface + 0x0242 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x000002000119633A _Z10sqljsParseP13sqljsDrdaAsCbP14db2UCinterface + 0x0246 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x000002000118E172 address: 0x000002000118E172 ; dladdress: 0x000002000000D000 ; offset in lib: 0x0000000001181172 ; (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020001192AE0 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 0x0380 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020000F2EDB6 _ZN8sqeAgent6RunEDUEv + 0x014e (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020002EB67AC _ZN9sqzEDUObj9EDUDriverEv + 0x0198 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020002EB67C6 _Z10sqlzRunEDUPcj + 0x0016 (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000020002006E42 sqloEDUEntry + 0x034a (/dbc/home/dbcsib01/sqllib/lib64/libdb2e.so.1) 0x0000004D2FE14974 address: 0x0000004D2FE14974 ; dladdress: 0x0000004D2FE0D000 ; offset in lib: 0x0000000000007974 ; (/lib64/libpthread.so.0) 0x0000004D2FCD3D96 address: 0x0000004D2FCD3D96 ; dladdress: 0x0000004D2FBE2000 ; offset in lib: 0x00000000000F1D96 ; (/lib64/libc.so.6) </StackTrace> DB2diag.log has: 2012-05-19-15.09.16.873630-240 E24739564A1118 LEVEL: Warning PID : 3961 TID : 2199342016848PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : DSNDB2 APPHDL : 0-52823 AUTHID : db2inst1 EDUID : 27 EDUNAME: db2agentg (DSNDB2 ) FUNCTION: DB2 UDB, DRDA Application Requester, sqljrParseSetSqlEnvReply, probe:900 MESSAGE : ADM2506W While an application was attempting to issue a deferred SET statement, the server returned a non-zero sqlcode. The sqlcode is "-725". Check your application, and validate the deferred SET statement. DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -725 sqlerrml: 21 sqlerrmc: CLIENT ACCTNG DSNDB2 sqlerrp : DSNLXENV sqlerrd : (1) 0xFFFFFF92 (2) 0x00000000 (3) 0x00000000 (4) 0xFFFFFFFF (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 42721 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 10.1 FP2 or later * **************************************************************** | |
Local-Fix: | |
Modify the application to set the CLIENT ACCTNG value to less than 256 characters. | |
Lösung | |
Upgrade to 10.1 FP2 or later | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.06.2012 10.10.2017 10.10.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |