|
Problem IC90425
|
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 CONNECT / DB2CONNCT / 970 - 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 9.7 FP9 *
**************************************************************** |
| Local Fix: |
None. Disabling LDAP is a work-around:
db2set DB2_ENABLE_LDAP=NO |
| available fix packs: |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 9.7 FP9 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC96386 IC96416
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.02.2013
17.12.2013
17.12.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.9
|
 |
| 9.7.0.9
|
|
