No, what I have is

PACKAGE
procedure a
code
procedure b
code calling procedure a
procedure c
code calling procedure b
END
What I want to do is trap a fatal error in procedure a, without letting control pass back to b and then c (where there might be other errors directly attributable to the original). I'm really looking for an "abort processing" command to stop cleanly. I don't really want to set variables in the exception handler of "a" and then check them after every call (there are lots), and I can't "raise_application_error" as that generates more superfluous messages in the final application.

Its a right pain-in-the-arse

R

> Message du 05/03/08 15:24
> De : "Luis Cardenas "
> A : ROGER.[Email address protected]
> Copie à :
> Objet : RE: packaged exceptions
>
> **A LazyDBA.com subscriber has responded to your lazydba.com post**
> **LazyDBA.com mail shield has forwarded you this email,
> **and removed any attachments, and kept your email address secret
> **from this person, and any viruses/trojans.
> **If you reply to this email, the person will see your email address as normal
> **Anything below this line is the original email text
>
>
> One way I have done it in the past was create an exception handling package and then called it from within other packages.
>
> Not much help sorry.
>
> Luis
>
> -----Original Message-----
> From: Roger TEDMAN [Email address protected]
> Sent: 05 March 2008 14:08
> To: LazyDBA Discussion
> Subject: packaged exceptions
>
>
> Hi all,
>
> I have a package containing several procedures (no surprise there), and I want to set up a common exception handler. I can create a declaration globally, but can I create a handler also?
>
> R
>
>
>

Oracle LazyDBA home page