|
Problem IC66705
|
Status: Closed |
TO PROVIDE THE SUPPORT FOR LDAP FOR CLI ODBC DRIVER (DS DRIVER) WHICH IS MISSING AND DOCUMENTED IN INFOCENTER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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: *
* 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
* 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 either DB2 V97fp2 or V95fp6 fixpack of data *
* server driver to resolve the LDAP connectivity problem. *
**************************************************************** |
| Local Fix: |
First fixed in V97fp2 |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in V97fp2.
Customer will able to connect to database cataloged in LDAP
server by specifying Database keyword in connection string. |
| Workaround |
Use data server driver configuration file to store the
information for the cataloged databases which are available in
LDAP . |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66823
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.02.2010
24.03.2010
24.03.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
