Search Results dbms_aqin




Overview
Explore in AI Chat

Overview

SYS.DBMS_AQIN is the internal Oracle Database package that implements the server-side enqueue and dequeue logic for the Advanced Queuing (AQ) subsystem. Within Oracle E-Business Suite 12.1.1 and 12.2.2, it functions as the low-level engine beneath the publicly documented DBMS_AQ and DBMS_AQADM interfaces. Business users never call DBMS_AQIN directly; instead, EBS components such as Workflow Mailer, the Notification System, Concurrent Manager, and various integration adapters rely on it transparently whenever a message is placed on or removed from an AQ queue.

The package is owned by SYS and is marked VALID in the documented metadata. Its classification is OTHER, reflecting that it is an Oracle-supplied kernel package rather than an EBS application object. It is exposed publicly through a synonym so that other SYS packages and any session with the appropriate privileges can reference it, but Oracle does not document its callable interface as supported customer API. In EBS 12.1.1 and 12.2.2 the package is present in both the database tier and in the context of the EBS schema, where the APPS schema and product schemas may resolve DBMS_AQIN through synonyms or qualified references during queue operations.

Key Procedures and Functions

The ETRM metadata documents no public procedures or functions for DBMS_AQIN. This is consistent with its role as a proprietary internal package: its entry points are callable only by Oracle kernel code and by the DBMS_AQ / DBMS_AQADM layer, and Oracle deliberately omits them from published documentation. The dependency data shows that DBMS_AQIN depends upon DBMS_AQ and DBMS_AQADM, and that DBMS_AQADM_SYS in turn references DBMS_AQIN. Practically, the package encapsulates the routines that perform the actual enqueue and dequeue work once the public DBMS_AQ API has validated arguments and resolved the queue. Because no signatures are published in the ETRM record, developers should never attempt to invoke DBMS_AQIN procedures directly; doing so risks unsupported behavior across patch levels and database upgrades.

Tables Accessed

DBMS_AQIN references a fixed set of SYS-owned AQ dictionary and message-format objects. These include AQ$_AGENT, AQ$_RECIPIENTS, AQ$_SUBSCRIBERS, and AQ$_SIG_PROP, which describe queue agents, recipient lists, subscriber registrations, and signature propagation metadata. It also references the JMS message type objects AQ$_JMS_BYTES_MESSAGE, AQ$_JMS_MAP_MESSAGE, AQ$_JMS_OBJECT_MESSAGE, AQ$_JMS_STREAM_MESSAGE, and AQ$_JMS_TEXT_MESSAGE, along with the generic ANYDATA type. These objects are used to construct, transform, and unpack messages as they move through the queue, particularly when EBS integrations exchange JMS-formatted payloads. The ETRM record lists no APPS-synonym tables accessed by the package, which reflects the fact that all queue storage and metadata reside in the SYS schema under AQ-managed tables.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, DBMS_AQIN is invoked implicitly whenever an application calls DBMS_AQ.ENQUEUE or DBMS_AQ.DEQUEUE. Typical EBS touchpoints include Oracle Workflow notification delivery, Business Event System message propagation, XML Gateway, and custom concurrent programs that publish to or consume from AQ queues. Because it is a SYS-owned internal package with no documented callable procedures, it should not be referenced in custom forms, concurrent programs, or PL/SQL packages.

  • Do not call DBMS_AQIN procedures directly; use the supported DBMS_AQ and DBMS_AQADM APIs instead.
  • It is referenced by one other documented package, DBMS_AQADM_SYS, and is publicly exposed via a synonym.
  • Troubleshooting AQ behavior in EBS should focus on DBMS_AQ and DBMS_AQADM, since DBMS_AQIN is not a supported customization surface.
  • Presence of DBMS_AQIN as VALID confirms the AQ subsystem is correctly installed in the database.