DB2 - Problembeschreibung
Problem IC84237 | Status: Geschlossen |
DB2 INSTANCE MAY CRASH WITH SIGNAL #11 when authentication type data encryption is in use. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
The DB2 instance may crash with signal #11 with authentication type data encrypt. A variety of problems may be reported as the core problem is a general corruption of memory however in the diagnostic data the following stack trace identifying the incident as this problem should exist: 0x000000000000F56C ?unknown + 0x0 0x090000000862F0DC sqljcReadBytesSplit__FP10sqljCmnMgrPvl + 0xB4 0x09000000064196EC sqljcReadBytesSplit__FP10sqljCmnMgrPvl@glue1028 + 0x74 0x0900000006442A44 sqljsCopySplitData__FP13sqljsDrdaAsCbP14DB2UCinterfaceP7DDValueP PcT4i + 0x264 0x09000000052E39D8 @45@sqljsDrdaAsCBGetDataPtr__F16SQLDD_TYPE_CLASSP14DB2UCinterfac eP10sqlz_valueP7DDValuePPcT5Pi + 0x260 0x0900000005A3C51C @45@sqlribniCbDrdaSwitch__FP14DB2UCinterfaceP8sqlrr_cbP20sqlri_o pparm_bni_argP7DDValuelT5P11bindinState - 0xA8 0x0900000005A3C2EC sqlribniCbDrda__FP14DB2UCinterface + 0x13C 0x0900000005A3BB94 sqlribni__FP8sqlrr_cb - 0x50 0x0900000005A0B84C sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm - 0x7E8 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All user prior to this release * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please upgrade to the latest release * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.06.2012 03.12.2012 03.12.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |