home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC73995 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use non-single byte SQL comments in CLI based      * 
* applications.                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* 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.             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to V9.1 FixPack 11 or later.                  * 
****************************************************************
Local Fix:
Please remove multi-byte chracters from SQL comments.
available fix packs:
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
This problem is first fixed in DB2 V9.1 FixPack 11.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC74008 IC74009 IC74698 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.01.2011
19.12.2011
19.12.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.11 FixList