|
Problem IC69962
|
Status: Geschlossen |
LDAP CAN THROW UNHANDLED EXCEPTION WHEN SETTING DB2LDAPHOST USING DB2SET COMMAND. |
| Produkt: |
DB2 CONNECT / DB2CONNCT / 910 - DB2 |
| Problembeschreibung: |
LDAP can throw Unhandled exception when setting DB2LDAPHOST
using db2set command.
for example
db2set DB2LDAPHOST=LDAP Server hostname or IP address:389
The stack trace of the exception dump contains the call to
sqloLdapConnect just before throwing exception.
The error can happen only when LDAP is unable to retrieve the
naming context of LDAP server.
A naming context or suffix is a DN that identifies the top entry
in a locally held directory hierarchy.
For example naming context cn=schema contains the LDAP
accessible representation of the schema.
Even though exception is thrown the LDAPHOST variable is set
properly which can be verified by issuing
db2set DB2LDAPHOST command. The exception can cause problem when
there unattended installation on windows platform that need to
be done on many machines and the script is setting DB2LDAPHOST
variable . |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* The problem can happen on all DB2 platform. *
****************************************************************
* PROBLEM DESCRIPTION: *
* LDAP can throw Unhandled exception when setting DB2LDAPHOST *
* using db2set command. *
* for example *
* db2set DB2LDAPHOST=LDAP Server hostname or IP address:389 *
* The stack trace of the exception dump contains the call to *
* sqloLdapConnect just before throwing exception. *
* *
* The error can happen only when LDAP is unable to retrieve *
* the naming context of LDAP server. *
* A naming context or suffix is a DN that identifies the top *
* entry in a locally held directory hierarchy. *
* For example naming context cn=schema contains the LDAP *
* accessible representation of the schema. *
* Even though exception is thrown the LDAPHOST variable is set *
* properly which can be verified by issuing *
* db2set DB2LDAPHOST command. The exception can cause problem *
* when there unattended installation on windows platform that *
* need to be done on many machines and the script is setting *
* DB2LDAPHOST variable . *
****************************************************************
* RECOMMENDATION: *
* On windows platform user need to acknowledge the exception *
* error message box. Even though exception is thrown, the *
* LDAPHOST variable is set properly which can be verified by *
* issuing db2set DB2LDAPHOST command *
**************************************************************** |
| Local-Fix: |
There is no fix in case exception is thrown in db2set
DB2LDAPHOST command . But even though exception is thrown, the
LDAPHOST variable is set properly which can be verified by
issuing db2set DB2LDAPHOST command. Thus the exception doesnot
limit or hinder the functionality of db2set DB2LDAPHOST
command. |
| verfügbare FixPacks: |
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
|
| Lösung |
First fixed in V91fp10. The error can happen only when LDAP is
unable to retrieve the naming context of LDAP server. If the
LDAP is setup properly and LDAP host or IP address is specified
correctly then db2set DB2LDAPHOST command will complete without
any exception. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC69964 IC69965 IC70527
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 15.07.2010
23.06.2011
23.06.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.1.FP10
|
| Problem behoben lt. FixList in der Version |
| 9.1.0.10
|
 |
