|
Problem IC96416
|
Status: Closed |
DB2 CONNECT INSTANCE MAY CRASH IN THE FUTURE AFTER A COMMUNICATI ON ERROR WHEN LDAP SUPPORT IS ENABLED (DB2_ENABLE_LDAP=YES). |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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 |
| available fix packs: |
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
|
| Solution |
Problem first fixed in DB2 10.5 FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.09.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
