|
Problem IC95492
|
Status: Geschlossen |
SQL1001N ERROR FROM CLI APPLICATION WHEN ENLISTING THE DATABASE WITH MSDTC. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - 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 V10.5 on LUW users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.5 Fix Pack4 or higher. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
Fixed in DB2 V10.5 Fix Pack 4. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.08.2013
08.09.2014
08.09.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.4
|
 |
