home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC76978 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.7 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.06.2011
29.03.2012
29.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList