<div>
I want X to silently fail, and A does not need to know about it. <br />
<br />
X does write to an error table as part of handling its own exception, but I want that to be the last thing that happens...I do not want X or A to continue.<br />
<br />
Thanks!
</div>


<div>
Thanks everyone--I am working on trying a solution.
</div>


<div>
Thanks to everyone for chipping in a suggested solution. I ended up solving it myself in a different way:<br />
<br />
I raised an unhanded exception in X, which then propagated it to A, which handled it, thus killing the rest of the process in A. &nbsp;I called the exception &quot;stop_exception&quot; and had to declare it in both X and A, but handled it only in my outermost block, A.<br />
<br />
Since I didn't use any of the solutions, I split the points, 100 for each comment.<br />
<br />
Thanks again,<br />
Alex
</div>


<div>
<div class="content wysiwyg-content">
Lets say I have two packages, each with one procedure (as a simplified example):<br />
<br />
PACKAGE_1.PROCEDURE_A is a very long procedure with a bunch of steps. &nbsp;Mid-way through it calls PACKAGE_2.PROCEDURE_X. &nbsp;Lets say that mid-way through PACKAGE_2.PROCEDURE_X I encounter a problem, and raise an exception. &nbsp;The exception uses RAISE_APPLICATION_ERROR to stop the procedure, but this causes an un-user-friendly message to be displayed in my application. &nbsp;I am looking for a way to simply exit/stop/kill the entire procedure, as if PACKAGE_1.PROCEDURE_A had completed without a hitch. &nbsp;The reason I want to do this is because as part of my exception handling I insert errors messages into a table, which is subsequently reflected nicely through the UI. &nbsp;<br />
<br />
How can I make the procedures stop running without using RAISE_APPLICATION_ERROR?<br />
<br />
Thanks,<br />
Alex Porter
</div>
</div>


Lets say I have two packages, each with one procedure (as a simplified example):

PACKAGE_1.PROCEDURE_A is a very long procedure with a bunch of steps.  Mid-way through it calls PACKAGE_2.PROCEDURE_X.  Lets say that mid-way through PACKAGE_2.PROCEDURE_X I encounter a problem, and raise an exception.  The exception uses RAISE_APPLICATION_ERROR to stop the procedure, but this causes an un-user-friendly message to be displayed in my application.  I am looking for a way to simply exit/stop/kill the entire procedure, as if PACKAGE_1.PROCEDURE_A had completed without a hitch.  The reason I want to do this is because as part of my exception handling I insert errors messages into a table, which is subsequently reflected nicely through the UI.  

How can I make the procedures stop running without using RAISE_APPLICATION_ERROR?

Thanks,
Alex Porter

Exit/stop/kill PLSQL procedure

Oracle is an object-relational database management system. It supports a large number of languages and application development frameworks. Its primary languages are SQL, PL/SQL and Java, but it also includes support for C and C++. Oracle also has its own enterprise modules and application server software.