home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT02948 Status: Closed

NON-DEFAULT LDAPSERVERPORT CAN'T BE CONFIGURED IN DB2DSDRIVER.CFG

product:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problem description:
In db2dsdriver.cfg in <ldapserver> section the parameters 
required to configure LDAP server can be specified . 
If the user is configuring the LdapServerPort other than 
standard 389 port then the value specified in the LdapServerPort 
parameter does not take effect and the database connection with 
the database cataloged in LDAP will fail with SQL3269N 
 
SQL3269N  DB2 was not able to access information in the LDAP 
directory because the LDAP server was not available. 
 
Example: 
      <configuration> 
         <ldapserver> 
             <parameter name="LDAPServerHost" 
value="LdapServerHostName"/> 
             <parameter name="LDAPServerPort" value="5859"/> 
         </ldapserver> 
    </configuration>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all DB2 users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1 or newer fixpack      * 
****************************************************************
Local Fix:
Specify the non standard LDAP server port number along with in 
LDAPServerHost parameter . for eg 
<parameter name="LDAPServerHost" 
value="LdapServerHostName:5859"/>
Solution
Problem was first fixed in DB2 Version 10.5 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.07.2014
27.03.2015
27.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList