home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC96416 Status: Geschlossen

DB2 CONNECT INSTANCE MAY CRASH IN THE FUTURE AFTER A COMMUNICATI ON ERROR
WHEN LDAP SUPPORT IS ENABLED (DB2_ENABLE_LDAP=YES).

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
If LDAP support is enabled (DB2_ENABLE_LDAP=YES) and a 
communication error occurs, then a timing error may cause DB2 
Connect to crash at some time in the future. An Exception 
C0000005 will occur, with a stack similar to this: 
 
 sqeDatabase::DeRegisterApp 
 sqeGatewayDatabase::StopUsingGatewayDatabase 
 sqleUCagentConnectReset 
 sqljsCleanup 
 sqljsDrdaAsInnerDriver 
 sqljsDrdaAsDriver 
 sqeAgent::RunEDU 
 sqlzRunEDU 
 sqloEDUEntry
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Connect users with LDAP enabled                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP3                                      * 
****************************************************************
Local-Fix:
None. Disabling LDAP is a work-around: 
 db2set DB2_ENABLE_LDAP=NO
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem first fixed in DB2 10.5 FP3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.09.2013
27.02.2014
27.02.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList