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

SELECT INTO IN COMPOUND STATEMENT DISALLOWED WHEN ISSUED BY CLI OR JDBC

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If your application uses CLI or JDBC to issue a dynamic 
SELECT INTO or VALUES INTO statement contained inside a 
compound statement, DB2 will report SQLCODE -109 when the 
statement is prepared.  The error occurs for SQL PL compiled 
compound statements, as well as PL/SQL anonymous blocks. 
 
 
For example, you will obtain SQLCODE -109 if you attempt to 
prepare the following compound statement via JDBC: 
 
begin 
  declare test varchar(10); 
  select 'abc' into test from sysibm.sysdummy1; 
 
  set ? = test; 
end
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If your application uses CLI or JDBC to issue a              * 
* dynamicSELECT INTO or VALUES INTO statement contained inside * 
* acompound statement, DB2 will report SQLCODE -109 when       * 
* thestatement is prepared.  The error occurs for SQL PL       * 
* compiledcompound statements, as well as PL/SQL anonymous     * 
* blocks.For example, you will obtain SQLCODE -109 if you      * 
* attempt toprepare the following compound statement via       * 
* JDBC:begindeclare test varchar(10);select 'abc' into test    * 
* from sysibm.sysdummy1;set ? = test;end                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 2.                       * 
****************************************************************
Local Fix:
As a workaround, convert the compound statement to an SQL 
procedure, and then call the procedure from CLI or JDBC.  For 
example: 
 
create or replace procedure workaround(out result varchar(10)) 
begin 
  select 'abc' into result from sysibm.sysdummy1; 
 
end
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in DB2 Version 9.7 Fix Pack 2.
Workaround
See LOCAL FIX.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66886 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.02.2010
05.07.2010
05.07.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList