Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC69962 Status: Closed

LDAP CAN THROW UNHANDLED EXCEPTION WHEN SETTING DB2LDAPHOST USING DB2SET
COMMAND.

product:
DB2 CONNECT / DB2CONNCT / 910 - DB2
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 .
Problem Summary:
**************************************************************** 
* 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.
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
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
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69964 IC69965 IC70527 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.07.2010
23.06.2011
23.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 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.