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

Error when CLPPlus performs environment variable substitution for SQL
statement that includes % character

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When executing a SQL statement that includes a % character, 
CLPPlus is not escaping these characters even when the escape 
character ('\') is placed before them. 
 
As a result, the following error is dumped: 
 
"The statement is too long or too complex. Current SQL statement 
size is #. ERRORCODE=-101, SQLSTATE=54001"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Error when CLPPlus performs environment variable             * 
* substitution for SQL statement that includes % character     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v105fp3.                                      * 
****************************************************************
Local Fix:
set ENVVARSUBSTITUTION OFF
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
09.09.2014
09.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList