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

CREATE OR REPLACE PACKAGE BODY WITH CURSOR VARIABLE FAILS WITH SQL0601N

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
CREATE OR REPLACE PACKAGE BODY may fail with SQL0601N if the 
body contains a cursor variable.  This will happen if the cursor 
variable already exists in the PL/SQL package.  For example: 
 
  create or replace package pack1 as end 
  DB20000I  The SQL command completed successfully. 
 
  create or replace package body pack1 as 
    cursor c1 is (select ibmreqd from sysibm.SYSDUMMY1); -- 
  end 
  DB20000I  The SQL command completed successfully. 
 
  create or replace package body pack1 as 
    cursor c1 is (select ibmreqd from sysibm.SYSDUMMY1); -- 
  end 
  SQL0601N  The name of the object to be created is identical to 
  the existing name "SCHEMA.PACK1.C1" of type "VARIABLE". 
  LINE NUMBER=3. SQLSTATE=42710 
 
This second CREATE OR REPLACE should succeed and replace the 
definition of the cursor variable PACK1.C1.
Problem Summary:
The fix is provided in the v97fp5
Local Fix:
Drop and recreate the PL/SQL package: DROP PACKAGE PACK1
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.05.2011
12.12.2011
12.12.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList