|
Problem IC68428
|
Status: Geschlossen |
SIGNAL #11 CRASH OR HIGH CPU USAGE WHEN IPV6 CLIENT CONNECTED. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
When an IPv6 client is connected to the database and LIST
APPLICATIONS is executed the server experience a Signal #11
crash with a stack similiar to the one below:
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00002ABCB8F72E8D ossDumpStackTraceEx + 0x01e5
(/home/db2instw/sqllib/lib64/libdb2osse.so.1)
0x00002ABCB8F6DC12 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00cc
(/home/db2instw/sqllib/lib64/libdb2osse.so.1)
0x00002ABCB63110DB sqlo_trce + 0x0365
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB6354B43 sqloEDUCodeTrapHandler + 0x0173
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x0000003CF800E930 address: 0x0000003CF800E930 ; dladdress:
0x0000003CF8000000 ; offset in lib: 0x000000000000E930 ;
(/lib64/libpthread.so.0)
0x00002ABCB4AC2E47
_ZN11sqeAppTable12AppTableIter17nextHashElemForDbEP11sqeDatabase
bb + 0x02eb
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB4BBD62B
_Z12sqlmonssagntj13sqm_entity_idP6sqlmaijPvP14sqlm_collectedttP5
sqlca + 0x14c7
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB4BECAC0 _Z15sqlmonssbackendP12SQLE_DB2RA_T + 0x0500
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB4A8DB8D _Z8sqlesrvrP14db2UCinterface + 0x05bd
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB4A9BE9D _Z19sqleMappingFnServerP5sqldaP5sqlca +
0x049d
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB4AEA2A4
_Z19sqlerKnownProcedureiPcPiP5sqldaS2_P13sqlerFmpTableP8sqeAgent
P5sqlca + 0x0270
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB4AEC21E _Z11sqlerCallDLP14db2UCinterfaceP9UCstpInfo +
0x0492
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB4B79D4A
_Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject +
0x0918
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
0x00002ABCB6FF978F
_Z21sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2U
Cinterface + 0x007d
(/home/db2instw/sqllib/lib64/libdb2e.so.1)
...
...
</StackTrace>
Other symptoms may be 100% CPU usage or hang. |
| Problem-Zusammenfassung: |
Will be fixed in next release of DB2. |
| Local-Fix: |
Revert clients to IPv4 |
| Lösung |
|
| Workaround |
See LOCAL FIX. |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 05.05.2010
06.05.2010
06.05.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
