DB2 - Problembeschreibung
Problem IC85724 | Status: Geschlossen |
CREATE OR REPLACE PACKAGE BODY STATEMENT THAT CONTAINS A PROCEDURE OR FUNCTION DECLARATION RETURNS ERROR SQL0454N | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
In PL/SQL, the CREATE PACKAGE BODY statement can contain private declarations of procedures or functions (also known as a "forward declarations", "routine prototypes", "procedure prototypes" or "function prototypes"). Although DB2 tolerates the presence of forward declarations in PL/SQL package bodies, it has not supported them properly. Without this APAR fix, a CREATE PACKAGE BODY statement that contains such a declaration might run without reporting any error code, but the procedure or function that it declares becomes a public element of the package (which means that it could be referenced from outside of the package). Without this APAR fix, when you create a package body with a procedure declaration, replace the package body with a CREATE OR REPLACE PACKAGE BODY statement, then issue the CREATE OR REPLACE PACKAGE BODY statement a second time, you get error SQL0454N, as the following examples demonstrate. Suppose that you have created a package, as follows: create or replace package pkg as procedure p1; end pkg@ Now suppose that you have supplied an implementation of this package, in which the public routine P1 calls a private routine P2, which first appears with a forward declaration in the package body. Without this APAR fix, the first time you run the CREATE OR REPLACE PACKAGE BODY statement, you will receive no error code, but when you run it again you will receive error SQL0454N: create or replace package body pkg as -- Forward declaration of private procedure P2 procedure p2; -- Implementation of public routine P1: procedure p1 as begin p2(); -- call the private routine end; -- Implementation of private routine P2: procedure P2 as begin null; end; end pkg@ The same problem can occur with a forward declaration of a private package function: drop package pkg@ create or replace package pkg as procedure p1; end pkg@ create or replace package body pkg as -- Forward declaration of private function F2 function f2(N in integer) return integer; -- Implementation of public routine P1: procedure p1 as N integer; begin N := f2(42); -- invoke the private function end; -- Implementation of private function F2: function f2(in N integer) return integer as begin return N * -10; end; end pkg@ ... and then issue the CREATE OR REPLACE PACKAGE BODY statement a second time. DB2 will report error SQL0454N. The fix for this APAR will ensure that private PL/SQL package routines with forward declarations remain private, that they will not be visible outside of the package, and that they will be replaced correctly by CREATE OR REPLACE PACKAGE BODY statements. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 1. * **************************************************************** | |
Local-Fix: | |
As a workaround, remove the procedure or function declaration from the CREATE PACKAGE BODY statement. If you put the procedure or function declaration in the CREATE PACKAGE statement instead of the CREATE PACKAGE BODY statement then the procedure or function that it declares is a public element of the package (which means that it could be referenced from outside of the package). | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
This issue is first fixed in DB2 Version 10.1 Fix Pack 1. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.08.2012 06.11.2012 06.11.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |