Re: Help: PL/SQL Compile ERROR
Date: 8 Feb 1995 22:53:59 GMT
Message-ID: <3hbi27$b6h_at_gnho.caritas.ab.ca>
In article <tcsmith.92.000F56F9_at_csi.nb.ca>, tcsmith_at_csi.nb.ca says...
>
>Hello all,
>
>I'm having a problem compiling a PL/SQL package. I have supplied the code
and
>error results below. I would appreciate it if some kind sole would help
save
>my sanity and shed some light to what might be going here.
>
>
>I have defined the following package ...
>
>create or replace package daemon as
> function execute_system(command varchar2, timeout number default 10)
> return number;
> function execute_sql(command varchar2, timeout number default 10)
> return number;
> procedure stop(timeout number default 10);
>end daemon;
>/
>
>this compiled with now error - now I try to compile the foloowing body...
>
>01 create or replace package body daemon as
>02 function execute_system( command varchar2, timeout number default 10)
>return number is
>03 s number;
>04 result varchar2(20);
>05 command_code number;
06 pipe_name varchar2(30);
07 begin
08 pipe_name := dbms_pipe.unique_session_name; 09 dbms_pipe.pack_message('SYSTEM'); 10 dbms_pipe.pack_message(pipe_name); 11 dbms_pipe.pack_message(command);
>and I get the errors as follows...
>Errors for PACKAGE BODY DAEMON:
>LINE/COL ERROR
>-------- -----------------------------------------------------
8/7 PL/SQL: Statement ignored 8/20 PLS-00201: identifier 'DBMS_PIPE' must be declared 9/7 PLS-00201: identifier 'DBMS_PIPE' must be declared 9/7 PL/SQL: Statement ignored 10/7 PLS-00201: identifier 'DBMS_PIPE' must be declared 10/7 PL/SQL: Statement ignored 11/7 PLS-00201: identifier 'DBMS_PIPE' must be declared
>11/7 PL/SQL: Statement ignored
.... etc......
>Can anyone shed some light on this for me??????
>-Tim Smith
-- Ian Hariott ihariott_at_caritas.ab.ca I also have experience this error in the past, and it always occurs when I refer to an object before declaring it. I notice that dbms_pipe was not declared anywhere before you referenced it. Try declaring dbms_pipe before using it in your PL/SQL Code.Received on Wed Feb 08 1995 - 23:53:59 CET