DB2 - Problem description
Problem IC76978 | Status: Closed |
DB2LDCFG RETURNS SQL3260N AN UNEXPECTED ERROR OCCURRED WHEN ACCESSING THE LDAP DIRECTORY. ERRORCODE = "0" | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 for catalog * **************************************************************** * PROBLEM DESCRIPTION: * * On Windows, executing db2ldcfg returns: * * SQL3260N An unexpected error occurred when * * accessing the LDAP directory. Errorcode = "0" * * * * * * * * * * * * * * The SQL3260N is returned by mistake * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.7 FP5 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.06.2011 29.03.2012 29.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |