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

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

product:
DB2 FOR LUW / DB2FORLUW / 950 - 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 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.
Solution
This problem is first fixed in DB2 V9.5 FixPack 8.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2011
05.07.2011
05.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)