> I'm working with Oracle 10, and it appears that exceptions do not propogate
> from one package to another. Is this true, and if so, is there a way to
> change this?
Post a sample - exceptions are raised, not propagated.
If A.proc_1 calls A.proc_2, and A.proc2 encounters an
error, which is caught by an exception handler, that
error is handled. (That's the whole point of having
an exception handler).
If you want the error to be reraised (so that the
error handler in A.proc_1 pick it up), reraise the
error. That is accomplished by the RAISE statement.
For A.proc_2, you may read B.proc_1

Signature
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
William Robertson - 29 Sep 2007 13:04 GMT
On Sep 29, 10:05 am, Frank van Bortel <frank.van.bor...@gmail.com>
wrote:
> > I'm working with Oracle 10, and it appears that exceptions do not propogate
> > from one package to another. Is this true, and if so, is there a way to
[quoted text clipped - 18 lines]
>
> Top-posting is one way to shut me up...
Propagation is a valid term for the behaviour by which exceptions work
their way up the calling tree.
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/errors.htm#LNPLS00706
I agree though that there is no such cross-package limitation. An
example would help.
> I'm working with Oracle 10, and it appears that exceptions do not propogate
> from one package to another. Is this true, and if so, is there a way to
> change this?
Exceptions propagate in the same manner in 1gR2 as they did in 6.
No change has been made by Oracle.
If you want to communicate an exception you need to use RAISE or
RAISE_APPLICATION_ERROR. Demos in Morgan's Library at www.psoug.org
under EXCEPTION HANDING.

Signature
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org