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 IC84350 Status: Geschlossen

CLI0100E SQLSTATE 07001 RETURNED FROM VISUAL STUDIO QUERY BUILDER USING
DB2.NET PROVIDER

Produkt:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problembeschreibung:
SQL query built using Query Builder in Microsoft Visual Studio 
when executed against a DB2 database using IBM DB2.NET provider 
can result in a CLI0100E error when the query has certain 
keywords, such as "CASE", "WHEN", "THEN", "ELSE", and/or "END". 
 
AdoDotNetDataSourceInformation (not an IBM method) calls 
GetSchema (one of IBM's methods) to get a ReservedKeyword list. 
The GetSchema call does indeed generate the list but the 
keywords "CASE", "WHEN", "THEN", "ELSE", "END" are not in the 
list, so the designer does not treat those as reserved keywords. 
 
 
Queries work fine from DB2 command line, but only fails from 
Query builder and Microsoft Visual Studio using DB2 .NET 
provider. 
 
For example: 
SELECT CODE, CASE COUNTRY WHEN 'XX' THEN 'XXXX' WHEN 'YY' THEN 
'YYYY' ELSE 'ZZZZ' END AS "SOURCE" 
FROM DB2ADMIN.COUNTRY WHERE (CODE = ?) 
 
SQL Execution Error. 
 
Executed SQL statement:SELECT CODE, CASE COUNTRY WHEN 'XX' THEN 
'XXXX' WHEN 'YY' THEN 'YYYY' ELSE 'ZZZZ' END AS "SOURCE" 
FROM DB2ADMIN.COUNTRY WHERE (CODE = ?) 
 
Error Source: IBM.Data.DB2 
Error message; Error [07001][IBM] CLI0100E Wrong number of 
parameters. SQLSTATE=07001 
 
 
This APAR fixes the problem in the DB2 .NET provider.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on Windows                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FP 1 or higher                          * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 V10.1 FP 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
06.11.2012
06.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList