Search Results dbms_sys_error




Overview
Explore in AI Chat

Overview

SYS.DBMS_SYS_ERROR is an Oracle-supplied PL/SQL package body resident in the SYS schema. It is a low-level kernel utility rather than an applications-facing API, and within Oracle E-Business Suite 12.1.1 and 12.2.2 it serves as the standard exception-raising primitive used throughout the database and the EBS technology stack. Its principal business function is to provide a controlled, uniform mechanism for signalling and propagating Oracle errors with caller-supplied error numbers and formatted messages, so that application code can raise meaningful, context-specific failures instead of relying on generic exceptions.

The ETRM documentation records the object as VALID, classified as OTHER, with an owner of SYS and no documented procedures or functions exposed at the applications layer. Its significance in an EBS environment derives from its breadth of use: the object is referenced by 254 other database packages. That reference count confirms DBMS_SYS_ERROR as foundational infrastructure — most notably, the DBMS_STANDARD specification declares its RAISE_APPLICATION_ERROR interface, and the package is therefore invoked implicitly or explicitly by virtually every PL/SQL unit that raises a user-defined exception.

Key Procedures and Functions

ETRM records zero documented procedures or functions for this package body. This is consistent with its nature as an internal kernel package: its entry points are not published as an EBS API and are not intended for direct customer invocation. Functionally, the package supplies the implementation behind the error-raising interface familiar to developers as RAISE_APPLICATION_ERROR, accepting an error number in the user-defined range and an associated message, then raising that condition to the calling program unit.

  • Error raising interface — accepts a numeric error code and a message string and terminates the current program unit with that error.
  • Message construction — assembles the raised message text so that it surfaces to the client, concurrent program log, or forms session with its original context intact.
  • RAISE_APPLICATION_ERROR support — the underlying implementation relied upon by DBMS_STANDARD, which is how most EBS custom code reaches this package.

No parameter lists are documented in ETRM for this object and none should be assumed; developers should continue to call the supported DBMS_STANDARD / RAISE_APPLICATION_ERROR interface rather than addressing the package body directly.

Tables Accessed

The ETRM metadata records no tables referenced by DBMS_SYS_ERROR, whether directly or through APPS synonyms. This is expected: the package operates entirely on the PL/SQL runtime error stack and requires no persistent storage. There are consequently no application tables, no EBS interface or staging tables, and no concurrent manager tables to consider in the context of this object. The dependency listing shows only intra-schema references to SYS and STANDARD, and the object is not referenced by any database object in the reverse direction — a further indication that it sits at the base of the dependency hierarchy rather than participating in application data flows.

Usage Notes

DBMS_SYS_ERROR is encountered in EBS 12.1.1 and 12.2.2 almost exclusively through indirect invocation. Typical scenarios include:

  • PL/SQL API validation failures — EBS public APIs and their internal validation layers raise user-defined errors that ultimately pass through this package.
  • Concurrent program error handling — a concurrent program that raises a user-defined error writes the resulting message to the request log; the raised text originates here.
  • Oracle Forms and OA Framework exceptions — form triggers and controller code raising application errors route through the same mechanism.
  • Custom code and extensions — customer-developed packages in the APPS schema that call RAISE_APPLICATION_ERROR depend on this package body at runtime.

Because the object is owned by SYS and classified as OTHER with no published API, it must not be modified, recompiled out of sequence, or referenced directly by custom code. Its status should be monitored as part of standard EBS health checks: an invalid DBMS_SYS_ERROR package body would cascade across the 254 dependent packages and could cause widespread runtime failures. Remediation should be limited to recompiling the package (or running the appropriate catalog scripts) under Oracle Support guidance, never to editing the body.