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

CLI MAY TRUNCATE MULTI-BYTES CHARACTERS IN SQL COMMENTS, IT RESULTS IN
SQL0104N.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
CLI applications might returns SQL0104N if the SQL includes SQL 
comments with multi-bytes characters. 
NOTE: The error code varies where the SQL comment is inserted. 
 
On non-English environment, CLI truncates multi-bytes character 
in SQL comments. 
For example, the following code fails with SQL0104N if the 
program runs in Japanese environments (e.g. LANG=Ja_JP or 
DB2CODEPAGE=943). 
 
 SQLHANDLE hstmt; 
 SQLCHAR *stmt = (SQLCHAR *)"SELECT * FROM T1 where 
C1=\n--<Japanese character(s)>\n10"; 
  <snip> 
 RC = SQLExecDirect(hstmt, stmt, SQL_NTS); 
 
The truncated (invalid) character codes might generate several 
kinds of SQL errors on database servers.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use CLI based applications in non-English          * 
* environments.                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* CLI applications might returns SQL0104N if the SQL includes  * 
* SQL comments with multi-byte characters.                     * 
* NOTE: The error code varies where the SQL comment is         * 
* inserted.                                                    * 
*                                                              * 
* On non-English environment, CLI truncates multi-byte         * 
* character in SQL comments.                                   * 
* For example, the following code fails with SQL0104N if the   * 
* program runs in Japanese environments (e.g. LANG=Ja_JP or    * 
* DB2CODEPAGE=943).                                            * 
*                                                              * 
* SQLHANDLE hstmt;                                             * 
* SQLCHAR *stmt = (SQLCHAR *)"SELECT * FROM T1 where           * 
* C1=\n--<Japanese character(s)>\n10";                         * 
* <snip>                                                       * 
* RC = SQLExecDirect(hstmt, stmt, SQL_NTS);                    * 
*                                                              * 
* The truncated (invalid) character codes might generate       * 
* several kinds of SQL errors on database servers.             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to V9.5 FixPack 8 or later.                   * 
****************************************************************
Local-Fix:
Please remove multi-byte chracters from SQL comments.
Lösung
This problem is first fixed in DB2 V9.5 FixPack 8.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.01.2011
05.07.2011
05.07.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP8
Problem behoben lt. FixList in der Version