|
Problem IC72406
|
Status: Geschlossen |
DB2 INSTALL IS OVERWRITING THE USER'S LDAP CONFIGURATION FILE. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problembeschreibung: |
DB2 provides a sample IBMLDAPSecurity.ini file, during DB2
install, that is used for SSL configuration. Unfortunately,
this file possesses the same file name as the real one a
customer would create and it is in the same location. Hence,
DB2 install would overwrite this file on every install.
You will get a "Can't contact LDAP server" error message in
db2diag.log:
2010-11-04-14.55.42.703000-240 I17220H288 LEVEL: Error
PID : 4528 TID : 6796
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage,
probe:20
DATA #1 : String, 76 bytes
InitLDAP: bind failed rc=81 (Can't contact LDAP server)
SearchDN='cn=myuser' |
| Problem-Zusammenfassung: |
****************************************************************
* 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 10. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.1 Fix Pack 11 or see "Local Fix" *
* portion for other suggestions. *
**************************************************************** |
| Local-Fix: |
Backup IBMLDAPSecurity.ini before you perform the DB2 install. |
| verfügbare FixPacks: |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Lösung |
The complete fix for this problem first appears in DB2 Version
9.1 Fix Pack 11 and all the subsequent Fix Packs. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC73719 IC75679
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 04.11.2010
20.12.2011
20.12.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.1.FP11
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.11
|
 |
