mcstock wrote:
> look into the WHEN OTHERS exception handler clause
>
> you can call a common procedure, passing the SQLCODE value to your routine
>
> also, sounds like you may be aware of this already, any unhandled exception
> gets propagated to the calling procedure -- so if you pass SQLCODE to your
> common procedure, it can then raise an appropriate exception (typically with
> RAISE_APPLICATION_ERROR) which would replace the one caught within the
> calling procedure, and pass it up the stack
>
> --mcs
>
>
> "Kid A" <paulkist_at_hotmail.com> wrote in message
> news:5327b5de.0311250730.4de56c2f_at_posting.google.com...
> | Hello everyone,
> |
> | I am setting up an exception handling framework for my stored
> | procedures. It seems as if there are thousands of possibilities of
> | errors that can occurr, how do you know which ones to go with.
> |
> | For example: I am making calls via DB link, and I am sure there are
> | 100 or so errors related to connection failures, authentication, etc.
> | Do I have to catch each error related to a remote call in order to
> | handle them, or is there way to group a bunch of exceptions together
> | in one handler, in order to handle all the remote connection problems
> | in ONE place in the code.
> |
> | Does this question make sense? I'd be interested to learn from your
> | experience with handling exceptions in PL/SQL.
> |
> | Thanks
> |
> | -PK
>
>
That would be a RAISE; a RAISE_APPLICATION_ERROR will do that,
at the specified point - a RAISE will re-raise the error to tha
calling unit
--
Regards, Frank van Bortel
Received on Wed Nov 26 2003 - 14:55:16 CST
