1. Database PL/SQL Language Reference
  2. PL/SQL Language Elements
  3. EXCEPTION_INIT Pragma

14.25 EXCEPTION_INIT Pragma

The EXCEPTION_INIT pragma associates a user-defined exception name with an error code.

The EXCEPTION_INIT pragma can appear only in the same declarative part as its associated exception, anywhere after the exception declaration.

Topics

Syntax

exception_init_pragma ::=

Description of exception_init_pragma.eps follows
Description of the illustration exception_init_pragma.eps

Semantics

exception_init_pragma

exception

Name of a previously declared user-defined exception.

error_code

Error code to be associated with exception. error_code can be either 100 (the numeric code for "no data found" that "SQLCODE Function" returns) or any negative integer greater than -1000000 except -1403 (another numeric code for "no data found").

Note:

NO_DATA_FOUND is a predefined exception.

If two EXCEPTION_INIT pragmas assign different error codes to the same user-defined exception, then the later pragma overrides the earlier pragma.

Usage Notes

The EXCEPTION_INIT pragma should only be used to associate an exception with an error number that is already meaningfully defined by Oracle. Note that any error number may be used by Oracle in the future, which can create conflicts with unrelated application use of that number.

Negative integers greater than -65536 are only partially supported. Currently, if left unhandled beyond the current layer of entry into PL/SQL, the exception is converted to ORA-6515 and the original exception is not recognized in the outer PL/SQL layer or client program.

Application-declared exceptions that are only raised and caught locally within a layer of entry into PL/SQL do not need the EXCEPTION_INIT pragma. The RAISE_APPLICATION_ERROR procedure and associated -20000 to -20999 range of error numbers should be used by application-declared exceptions that are intended to be recognizable in outer PL/SQL layers or in the client program.

Examples

  • Example 12-5, "Naming Internally Defined Exception"

  • Example 12-13, "Raising User-Defined Exception with RAISE_APPLICATION_ERROR"

  • Example 13-13, "Handling FORALL Exceptions After FORALL Statement Completes"

Related Topics

In this chapter:

In other chapters: