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

CLI QUERIES WHICH NEEDS INTERNAL TRANSLATION MAY THROW CLI0118E

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
CLI queries which needs internal translation, for eg. query 
using fn TimestampDiff function will internally be translated to 
use SYSFUN.TIMESTAMPDIFF instead, may throw error "CLI0118E 
Invalid SQL syntax.SQLSTATE=37000". This is because the length 
of the translated query is exceeding the allocated temporary 
buffer. In trace you may see failure in CLI_scnTranslate 
function 
 
1305278       31.954000729   | | | | CLI_scnReplaceToken entry 
1305279       31.954001518   | | | | CLI_scnReplaceToken error 
[probe 1] 
1305280       31.954001913   | | | | | CLI_errStoreError entry 
1305281       31.954002308   | | | | | CLI_errStoreError data 
[probe 999] 
1305282       31.954002703   | | | | | CLI_errStoreError exit 
1305283       31.954002703   | | | | CLI_scnReplaceToken exit 
[rc = 0xFFFFFFFF = -1] 
1305284       31.954002703   | | | | CLI_memFree entry 
1305285       31.954003097   | | | | CLI_memFree exit 
1305286       31.954003097   | | | CLI_scnTranslate exit [rc = 
0xFFFFFFFF = -1]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DB2 CLI users                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v10.5.7 or later                                  * 
****************************************************************
Local Fix:
Solution
fixed in v10.5.7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.03.2015
20.01.2016
20.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList