DB2 - Problembeschreibung
Problem IC93738 | Status: Geschlossen |
SQL1001N ERROR FROM CLI APPLICATION WHEN ENLISTING THE DATABASE WITH MSDTC. | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / A10 - DB2 | |
Problembeschreibung: | |
ODBC/ODBC.NET application using the db2dsdriver.cfg, receives the following error when it enlists the connection with MSDTC, if the database name is greater than 8 characters: SQLGetDiagRecW( pszSqlState="S1501", pfNativeError=-1001, pszErrorMsg="[IBM][CLI Driver] SQL1001N "longdbname" is not a valid database name. SQLSTATE=2E000 sample db2dsdriver.cfg: <configuration> <dsncollection> <dsn alias="DB2TEST" name="longdbname" host="host1.domain.com" port="47558"> <parameter name="Authentication" value="SERVER"/> </dsn> </dsncollection> <databases> <database name="longdbname" host="host2.domain.com" port="47558"> <parameter name="CommProtocol" value="TCPIP"/> <parameter name="enableDirectXA" value="true" /> </database> </databases> </configuration> The error can be reproduced by this script: opt autocommit on opt echo on opt calldiag on sqlallocenv 1 sqlallocconnect 1 1 sqlconnect 1 "DB2TEST" -3 "uid" -3 "pwd" -3 begintransaction 1 enlistconnect 1 1 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All DB2 on LUW V10.1 users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 Fix Pack 3. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 V10.1 Fix Pack 3. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95448 IC95492 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.06.2013 08.10.2013 08.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |