DB2 FOR LUW / DB2FORLUW / A10 - DB2

DB2 will terminate abnormally when calling an SQL procedure 
under the following conditions: 
 
- The procedure is declared with at least one OUT parameter of 
type CHAR; 
- The corresponding parameter in the CALL statement is a 
parameter marker that has been cast to an INTEGER type. 
 
For example: 
 
create or replace procedure proc1(out param CHAR(5)) 
begin 
end 
% 
call proc1(CAST(? as INTEGER)); 
% 
 
You will observe a stack trace similar to the following: 
 
ossDumpStackTraceEx 
OSSTrapFile6dumpEx 
sqlo_trce 
sqloEDUCodeTrapHandler 
__restore_rt 
sqlddFreeDD 
sqlnq_describe_call_parms 
sqlnq_describe 
sqlnn_cmpl 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
(truncated stack) 
 
ALSO : 
901 can be reported while executing CALL stmt with NOOP CAST on 
OUT/INOUT type parameter 
 
CREATE or replace PROCEDURE  P_INOUT 
INOUT RES FLOAT) 
begin 
end 
% 
CREATE or replace PROCEDURE CALLER1 
LANGUAGE SQL 
P1: 
BEGIN 
  DECLARE V1 FLOAT;-- 
  CALL  P_INOUT(double(V1));-- 
END 
%

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 2 or higher.                   * 
****************************************************************

Do not use CAST on OUT/INOUT parameter markers

DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 V10.1 Fix Pack 2. This is a server 
side fix.

See LOCAL FIX.

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

17.11.2012
19.04.2013
19.04.2013