|
Problem IC68839
|
Status: Closed |
DB2 LDAP PLUG-IN SOMETIMES FAILS WHEN CHASING REFERRALS. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
The DB2 LDAP plug-in sometimes fails when chasing referrals to
find a user or a group. An error will be logged in db2diag.log
to indicate the function ldap_search_s failed with rc=10. An rc
of 10 means referral was returned. Here is an example of such
a log entry:
2010-05-25-14.15.54.753000-240 I3897H412 LEVEL: Error
PID : 4216 TID : 628 PROC : db2.exe
INSTANCE: DB2 NODE : 000
EDUID : 628
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 117 bytes
db2ldapFindAttrib:
ldap_search_s failed rc=10 (Referral returned)
filter=(&(objectClass=user)(sAMAccountName=bob)) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 systems on all Linux, Unix and Windows platforms at *
* service levels from Version 9.1 GA through to Version 9.1 *
* Fix Pack 9. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 Fix Pack 10. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
The complete fix for this problem first appears in DB2 Version
9.1 Fix Pack 10 and all the subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC70634 IC70635 IC70636
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.05.2010
17.06.2011
17.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
