|
Problem IC69965
|
Status: Closed |
LDAP CAN THROW UNHANDLED EXCEPTION WHEN SETTING DB2LDAPHOST USING DB2SET COMMAND. |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - 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: *
* Users using Fixpack v97fp3a and before *
****************************************************************
* 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: *
* 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. *
**************************************************************** |
| 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.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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 |
First fixed in DB2_V97fp4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.07.2010
09.02.2011
09.02.2011 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
