It seems to me that there are a couple of possibilities here...

If B is catching and handling the exception, there should be no need for
A to know that there was a failure. There are generally some errors
that a procedure can catch and handle reasonably-- for example, a
procedure that sends email might retry a few times if a particular error
code were returned. It should not matter to B whether the email was
sent on the first try or not, merely that procedure A did what it was
supposed to do and sent the email.

If B is catching and not handling the exception, B would need to rethrow
the exception. If B has a WHEN OTHERS THEN NULL clause, for example,
you would need to address this design flaw. You may want B to catch all
exceptions and write to a log, but B should be re-throwing the exception
if it cannot recover from it.

Justin Cave
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

-----Original Message-----
From: Mohanty Deepak K (GE Consumer & Industrial consultant)
[mailto:oracledba-ezmlmshield-x6391041.[Email address protected]
Sent: Friday, October 29, 2004 2:01 AM
To: LazyDBA Discussion
Subject: Exception handller problem



HI
i have two procedure
one is Procedure A
2nd is Procedure B

Procedure A calls Procedure B .
Procedure B has exception handler inside it ,my problem is that i want
to know if any error occour in procedure B how can i know from procedure
A.

Thanks


--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html






Oracle LazyDBA home page