Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC76979 Status: Closed

DB2LDCFG RETURNS SQL3260N AN UNEXPECTED ERROR OCCURRED WHEN ACCESSING THE
LDAP DIRECTORY. ERRORCODE = "0"

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
db2ldcfg returns SQL3260N An unexpected error occurred when 
accessing the LDAP directory. Errorcode = "0" 
 
On Windows, run db2ldcfg returns: 
SQL3260N An unexpected error occurred when accessing the LDAP 
directory. Errorcode = "0" 
 
 
Note Errorcode=0 and db2trace shows no error. 
 
The SQL3260N is returned by mistake 
 
Users can ignore the error and proceed with their DB2 - ldap 
setup.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows DB2 LDAP users                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* On Windows, when executing db2ldcfg, it returns:             * 
* SQL3260N An unexpected error occurred when                   * 
* accessing the LDAP directory. Errorcode = "0"                * 
*                                                              * 
*                                                              * 
* The SQL3260N is returned by mistake                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.5 FP9                                          * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.5 Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.06.2011
22.08.2012
22.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList
9.5.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.