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

SQL20454N RC =2 WHEN OUTER JOIN OPERATOR "(+)" IS USED IN A
CURSOR WHICH IS DECLARED IN A PACKAGE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
SQL20454N error will be returned if a package is compiled which 
contains an outer join operator specified as "(+)" used in a 
cursor definition. For example the following package fails to 
compile: 
 
SET SQLCOMPAT PLSQL; 
 
create table T1(fk1 integer, fk2 integer); 
create table T2(pk1 integer, pk2 integer); 
 
drop package broken; 
 
create or replace package broken 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 broken; 
/
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.07.2013
23.06.2014
23.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList