home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC76081 Status: Geschlossen

SQLDRIVERCONNECT TRAPS/FAILS WHEN USED VIA 64-BIT ODBC APPLICATI ONS AND
SQL_DRIVER_PROMPT OR SQL_DRIVER_COMPLETE IS USED

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A 64-bit ODBC application running on Windows 64-bit platforms 
will either fail or trap when the ODBC application calls 
SQLDriverConnect (or SQLDriverConnectW) and the parameter option 
SQL_DRIVER_PROMPT or SQL_DRIVER_COMPLETE is used. 
 
These parameter options will launch a dialog box that prompts 
for the data source name (DSN) along with the userid and 
password.  The 64-bit DB2 ODBC/CLI driver has a problem reading 
the contents of the data source name and on platforms like 
Windows 7, the data source name that gets returned is " " (or 
single space). 
 
When DB2 then tries to locate this data source it will fail with 
the following error: 
 
SQL1013N  The database alias name or database name " " could not 
be found. 
 
 
When running on a platform like Windows 2003, the call to 
SQLDriverConnect will just trap, and the application will fail 
to connect. 
 
This problem can be seen in any ODBC 64-bit application such as 
the 64-bit versions of Microsoft Office or Microsoft Excel.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows users.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7, Fixpack 5                        * 
****************************************************************
Local-Fix:
Hard coding the userid and password in the db2cli.ini file will 
prevent the dialog box from opening up, and will workaround this 
problem. 
 
The following commands can be used to update the db2cli.ini file 
with the userid and password: 
 
db2 update cli cfg for section <DSN> using UID <userid> 
db2 update cli cfg for section <DSN> using PWD <password> 
 
... where <DSN> is the data source name, and <userid> and 
<password> are the userid and password that you would use to 
connect. 
 
Do note that the password will be stored in plain text in the 
db2cli.ini file and could be considered a security violation.
verfügbare FixPacks:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 9.7, Fixpack 5
Workaround
see Local Fix.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.04.2011
21.12.2011
21.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList