1

Topic: How to learn the present error in stored procedure at start?

Core-was  of type:

create or replace mysp (a number, b varchar2) is
begin
insert into sometable (a, b) values (mysp.a, mysp.b);
end;

Then a certain villain changed table structure sometable and now for a command:

$dbh-> do ("execute mysp (1, ' a ')");

I receive

DBD:: Oracle:: db do failed: ORA-00900: invalid SQL statement (DBD ERROR: OCIStmtExecute) [for Statement "execute mysp (1, ' a ')"] at mysript.pl

And here if to come in SQL Developer and launches procedure recompilation already we receive the correct errors (a column it is not found, the type does not coincide both  and ).
It is asked, it is possible-whether to receive at once at start  code of the present errors instead of the general ORA-00900? Or the presents are accessible only at recompilation?

2

Re: How to learn the present error in stored procedure at start?

Normally the Oracle produces the whole pack of errors. If the pearl-barley driver from them is capable to show
Only the first - to do nothing.

3

Re: How to learn the present error in stored procedure at start?

call mysp (1, ' a ');
?

4

Re: How to learn the present error in stored procedure at start?

[code] ORA-00900: invalid SQL statement [/quote] Is not present at   execute.

5

Re: How to learn the present error in stored procedure at start?

northern seas wrote:

call mysp (1, ' a ');
?

Usage call produced: ORA-06575: Package or function mysp is in an invalid state
However, when procedure completely the worker and execute it quite normally launches...
Strange it is all.
But I read this to dock: https://docs.oracle.com/cd/B19306_01/B1 … m#i1007682
About call there generally anything is not present.

6

Re: How to learn the present error in stored procedure at start?

White Owl wrote:

About call

a that there is written about execute?