Search Results dbms_apply_error




Overview

SYS.DBMS_APPLY_ERROR is a core Oracle database-supplied PL/SQL package installed in the SYS schema. In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, it provides the underlying infrastructure used by Oracle Streams and Advanced Replication to capture, store, and transmit runtime errors that occur during the application of replicated or captured messages. Its status is VALID and its API classification in the ETRM documentation is recorded as OTHER, indicating that it is not a business-facing EBS API but rather a database kernel-level package that EBS inherits through its dependence on the standard Oracle RDBMS.

Within an EBS context, DBMS_APPLY_ERROR is significant primarily because Oracle Streams and Advanced Replication are used in multi-tier deployments, information-sharing configurations, and certain data propagation scenarios (for example, between EBS instances or between an EBS database and downstream analytical stores). When an apply process encounters a message that cannot be applied, DBMS_APPLY_ERROR is responsible for persisting that error into a Streams error queue so that it can be inspected, retransmitted, or deleted.

Key Procedures and Functions

The ETRM metadata records zero documented procedures or functions for this package. This is expected: DBMS_APPLY_ERROR is part of Oracle Streams' internal infrastructure and most of its entry points are undocumented internal routines that operate on the error queue. Its public catalog entry is intentionally minimal, and no user-callable signatures are exposed in the standard EBS documentation set.

Functionally, the package works in conjunction with the documented administrative interface SYS.DBMS_APPLY_ADM, which is listed as a dependent that references DBMS_APPLY_ERROR. Administrative operations such as inspecting or purging apply errors are exposed through DBMS_APPLY_ADM and the related DBA_APPLY_ERROR / ALL_APPLY_ERROR dictionary views rather than through direct calls to DBMS_APPLY_ERROR.

Tables Accessed

The ETRM metadata does not document any tables referenced via APPS synonyms. This confirms that the package operates purely on Streams-owned dictionary objects in the SYS schema, most notably the error queue table underlying the *_APPLY_ERROR views. No EBS application tables (for example, in the AP, GL, or INV schemas) are accessed directly or through synonyms.

Usage Notes

Because DBMS_APPLY_ERROR is not documented as a callable EBS API and is referenced by only one other package (DBMS_APPLY_ADM), it should not be invoked directly from EBS forms, concurrent programs, or custom code. EBS customers and developers who need to diagnose Streams or Advanced Replication apply failures should use the supported administrative path: query DBA_APPLY_ERROR or ALL_APPLY_ERROR, then use DBMS_APPLY_ADM procedures to execute or delete individual error transactions. Direct manipulation of DBMS_APPLY_ERROR internals is unsupported and may corrupt the Streams error queue. In EBS 12.1.1 and 12.2.2, awareness of this package is therefore useful mainly for dependency analysis and troubleshooting, not for application-layer development.