DB2 - Problem description
Problem IC84610 | Status: Closed |
DYNAMIC SQL EXECUTION FAILS WITH SQL0138 WITH REOPT=ALWAYS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - 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 DB2 version 10.1 fix pack 1 * **************************************************************** | |
Local Fix: | |
Cast the untyped parameter marker to make a typed parameter marker, e.g.: SUBSTR( CAST( ? as VARCHAR(32672) ), <offset>, <length> ) | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 version 10.1 fix pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 19.11.2012 19.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |