| Error handling NEED HELP! [message #38997] |
Wed, 05 June 2002 08:13  |
sverch
Messages: 582
Registered: December 2000
|
Senior Member |
|
|
Hi,
I have a standalone procedure ("calling procedure") that calls about 30 another standalone procedures("called procedures"). I was asked to write a code that stops the entire process if any of these "called" procedures have a certain Oracle errors. I.e. if a "called" procedure had an error number of
such and such range then instead of simply handling an exception and moving to the next procedure the code in the "calling" procedure should stop the entire processing.
I tried to play with IN OUT parameters and with IF..THEN logic, but there is something flaky there and I cannot yet figure out what.
Any ideas?
|
|
|
|
| Re: Error handling NEED HELP! [message #38998 is a reply to message #38997] |
Wed, 05 June 2002 09:48  |
Todd Barry
Messages: 4819
Registered: August 2001
|
Senior Member |
|
|
I might approach this with a loop construct that requires only a single exception handler instead of one around each proc.
begin
for i in 1..3 loop
begin
if i = 1 then
proc1;
elsif i = 2 then
proc2;
elsif i = 3 then
proc3;
end if;
exception
when no_data_found or too_many_rows then
-- maybe log this somewhere
exit;
end;
end loop;
end;
The exception handling in your called procedures would have to either not trap for or re-raise the specific "fatal" conditions. They would have to handle any other exceptions.
I would also highly recommend that you do not put a:
block anywhere in your calling or called procedures. This will only suppress errors that should be handled at some level.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
