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

DYNAMIC SQL EXECUTION FAILS WITH SQL0138 WITH REOPT=ALWAYS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
A dynamic SQL statement may fail at execution time with SQL0138 
when REOPT is set to ALWAYS.  This can happen when the statement 
includes a SUBSTR function where the first argument is an 
untyped parameter marker and the offset and length arguments put 
the substring range outside the actual parameter marker value at 
execution time. 
 
This is similar to IZ08102 which is an APAR for stored 
procedures
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 Fix Pack 10                           * 
****************************************************************
Local Fix:
Cast the untyped parameter marker to make a typed parameter 
marker, e.g.: SUBSTR( CAST( ? as VARCHAR(32672) ), <offset>, 
<length> )
Solution
Problem was first fixed in Version 9.5 Fix Pack 10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84121 IC84610 IC87873 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.04.2012
11.12.2012
11.12.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList