DB2 FOR LUW / DB2FORLUW / A50 - DB2

If you have declared a parameterized cursor variable in a PL/SQL 
package, DB2 may report error SQL20454N with reason code "2" if 
the variable's initializer query uses one of the cursor 
parameters in conjunction with the outer join operator "(+)". 
For example: 
 
create table T1(fk1 integer, fk2 integer); 
create table T2(pk1 integer, pk2 integer); 
 
create or replace package PKG as 
cursor c1(v_pk1 in T2.pk1%TYPE) 
is 
  select * from T1, T2 
    where T1.fk1(+) = v_pk1 
      and T1.fk1(+) = T2.pk2; 
 
end PKG; 
/ 
 
You may see other errors when a parameter from a package cursor 
variable is used in the cursor query, including SQL0204N 
("<cursor parameter>" is an undefined name).

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This issue is due to the presence of a cursor parameter in a * 
* query, when the cursor is declared either as a global        * 
* variable or a PL/SQL package variable                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 4                   * 
****************************************************************

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 Version 10.5 and Fix Pack 4

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC94039 IC94040 
follow-up : 

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

11.07.2013
08.09.2014
17.10.2014