DB2 - Problembeschreibung
Problem IT08333 | Status: Geschlossen |
DB2CLI REFRESHLDAP TRUNCATES HOST DATABASE NAME | |
Produkt: | |
DB2 COMMON CLIE / DBCMNCLNT / A50 - DB2 | |
Problembeschreibung: | |
db2cli refreshldap updates and appends all configuration information in the IBM data server driver configuration file (db2dsdriver.cfg) with the configuration information that are specified on the Lightweight Directory Access Protocol (LDAP) server. However the entries in db2dsdriver.cfg for the DB2 for z/OS subsystems are invalid - the database names in sections <dsn> and <database> are truncated to 8 characters. For example LDAP entry stores the following information: db2databasealias: SAMPLE db2nodeptr: db2nodeName=... db2databasename: DATABSAMPLE description: DB2D on z/OS db2cli refreshldap generates db2dsdriver.cfg file: <configuration> <ldapserver> ... </ldapserver> <dsncollection> <dsn alias="SAMPLE" name="DATABSAM" host="test.ibm.com" port="40576? ldap=1> ... </dsn> </dsncollection> <databases> <database name="DATABSAM" host="test.ibm.com" port="40576"/> ... </database> </databases> </configuration> Please note the truncated database name. When user verifies this configuration using command: db2cli validate -dsn sample -connect - user <user_name> -passwd <user_password> the error SQL30061N will be generated: [FAILED]: [IBM][CLI Driver] SQL30061N The database alias or database name "DATABSAM " was not found at the remote node. SQLSTATE=08004 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 7 * **************************************************************** | |
Local-Fix: | |
Lösung | |
First fixed in Version 10.5 Fix Pack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.04.2015 10.02.2016 10.02.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |