Search Results dbms_xevent




Overview
Explore in AI Chat

Overview

DBMS_XEVENT is a package body owned by the XDB schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of Oracle's XML DB (XDB) infrastructure, which is embedded in the database and underpins XMLType storage, the XML DB Repository, resource management, and event-driven processing within the EBS database tier. The package provides the event abstraction layer used by XML DB to describe and manipulate events raised against repository resources — for example when a resource is created, updated, deleted, locked, or rendered. In the EBS context it is an internal, database-supplied package rather than an application-level API: it is not owned by APPS, it is classified as "OTHER" in the ETRM repository, and it is not referenced by any other database object. Its role is therefore foundational rather than business-facing, supporting the XDB repository features on which several EBS components (such as XML Publisher / BI Publisher XMLType operations and repository-based attachments) implicitly depend.

Key Procedures and Functions

The documented API surface contains 47 procedures and functions, of which the following 20 are explicitly recorded in the ETRM metadata. Accessor functions such as GETEVENT, GETXDBEVENT, GETRESOURCE, GETPARENT, GETPATH, GETLINK, GETLOCK, GETINTERFACE, GETNAME-style identifiers, GETAPPLICATIONDATA, GETHANDLERLIST, GETPARAMETER, GETOLDRESOURCE, GETUPDATEBYTEOFFSET, GETUPDATEBYTECOUNT, GETOPENACCESSMODE, GETOUTPUTSTREAM and GETCURRENTUSER retrieve attributes of an event or of the resource it concerns. ISNULL tests whether an event handle is uninitialized. SETRENDERSTREAM and SETRENDERPATH configure the rendering destination used when a resource is rendered by the XML DB rendering engine. Collectively these routines let a handler inspect the triggering resource, its path and parent, associated locks and links, the handler list bound to the event, application-supplied data, and the byte range affected by an update, before deciding whether to act.

Tables Accessed

ETRM records no application tables accessed through APPS synonyms, which is consistent with the package's status as internal XDB infrastructure. The dependency list instead shows references to XDB.DBMS_XDBEVENT_LIB, XDB.DBMS_XDBRESOURCE, XDB.XMLTYPE, SYS.DBMS_STANDARD and STANDARD. Any persistent state it touches resides in the XDB repository tables (such as XDB$RESOURCE and related configuration tables), accessed indirectly through those XDB dependencies rather than by direct SQL from this package body.

Usage Notes

DBMS_XEVENT is not intended for direct invocation from EBS forms, concurrent programs, or custom application code. It is called internally by the XML DB event subsystem and by XML DB repository handlers; the ETRM metadata confirms it is referenced by zero other database objects and that no other object depends on it at the PL/SQL level. Customizations should therefore avoid calling it directly, since its interface is undocumented, version-specific, and subject to change with database patches. It is most useful as a diagnostic object: DBAs and EBS technical consultants querying DBA_OBJECTS or DBA_DEPENDENCIES for DBMS_XEVENT are typically investigating XML DB internals, validating that XDB components are VALID after an upgrade or patch, or tracing repository event behaviour. Any troubleshooting should be confined to verifying object status and dependencies rather than altering or invoking the package.