|
Problem IC76903
|
Status: Closed |
DB2LDCFG RETURNS SQL3260N AN UNEXPECTED ERROR OCCURRED WHEN ACCESSING THE LDAP DIRECTORY. ERRORCODE = "0" |
| product: |
DB2 CONNECT / DB2CONNCT / 910 - DB2 |
| Problem description: |
db2ldcfg returns SQL3260N An unexpected error occurred when
accessing the LDAP directory. Errorcode = "0"
On Windows, executing 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.1 FP 11 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
Problem was first fixed in Version 9.1 Fix Pack 11 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC76978 IC76979 IC78500
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.06.2011
19.01.2012
19.01.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP11
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.11
|
 |
