DB2 - Problembeschreibung
Problem IC66823 | Status: Geschlossen |
TO PROVIDE THE SUPPORT FOR LDAP FOR CLI ODBC DRIVER (DS DRIVER) WHICH IS MISSING AND DOCUMENTED IN INFOCENTER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problembeschreibung: | |
As per the link the LDAP support for IBM Data Server Driver for ODBC and CLI is provided http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.i bm.db2.luw.apdv.cli.doc/doc/r0024158.html Though DB2 LDAP is supported for CLI ODBC and Data server Driver (DSDriver) , the connectivity may not work and customer might get following error messages SQL3273N The database "<database-alias>" was not found in the LDAP directory SQL3272N The node "<node-name>" was not found in the LDAP directory This error occurs becuase DB2 is not able to find the database or node which is cataloged in LDAP | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * User who are using LDAP for cataloging of databases using * * IBM data server driver or IBM CLI ODBC driver for DB2 * **************************************************************** * PROBLEM DESCRIPTION: * * Though DB2 LDAP is supported for CLI ODBC and Data server * * Driver * * (DSDriver) , the connectivity may not work and * * * * customer might get following error messages * * * * SQL3273N The database "<database-alias>" was not found in * * the * * LDAP directory * * * * SQL3272N The node "<node-name>" was not found in the LDAP * * * * directory * * * * This error occurs becuase DB2 is not able to find the * * database * * or node which is cataloged in LDAP * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2_v98fp3 * **************************************************************** | |
Local-Fix: | |
First fixed in V97fp2 | |
verfügbare FixPacks: | |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2_v98fp3 Customer will able to connect to database cataloged in LDAP server by specifying Database keyword in connection string. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.03.2010 20.12.2010 20.12.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
9.8.0.3 |