A script-enabled browser is required for this page to function properly.

About Using PL/SQL Exception Handling in Triggers

Errors in PL/SQL code are called exceptions. When an error occurs, an exception is raised. To handle raised exceptions, you can write exception handlers. In Oracle Forms, you can use exception handlers to handle runtime errors that occur in the following types of statements:

When one of these statements in a trigger or PL/SQL block raises an exception, normal processing stops and control transfers to the trigger's exception handling section.

How Exceptions Propagate in Triggers

PL/SQL blocks can be nested as in-line blocks in Oracle Forms triggers. For example, a trigger might include a block that encloses another block.

When the inner block raises an exception for which there is no exception handler, that block terminates and the exception propagates, or "falls out," to the enclosing block. If a handler is not found in the enclosing block, the exception propagates again, finally reaching the outermost block of the trigger. If the outer block does not handle the exception, the trigger fails, and Oracle Forms returns a runtime error.

Exceptions Raised in User-Named Subprograms

For purposes of exception handling, calls to user-named subprograms are treated as in-line PL/SQL blocks within a trigger. That is, an unhandled exception raised in a user-named subprogram propagates to the block in which the subprogram was called.


About handling runtime errors in triggers