Search Results dbms_prvtaqis




Overview
Explore in AI Chat

Overview

SYS.DBMS_PRVTAQIS is a private, Oracle-supplied PL/SQL package that forms part of the Advanced Queuing (AQ) infrastructure shipped with the Oracle database. In Oracle E-Business Suite 12.1.1 and 12.2.2, this package resides in the SYS schema and is marked VALID in the data dictionary. It is not an EBS application object; rather, it is a database kernel component on which EBS depends whenever workflow notification mailers, Business Event System (WF_BES), or AQ-based integration queues are used.

The name follows Oracle's convention for internal AQ packages: the "PRVT" prefix designates a private implementation package, and "AQIS" refers to the AQ Internet/SQL layer. DBMS_PRVTAQIS provides the internal callable interface that the public AQ APIs invoke to manipulate queue metadata, agent registrations, subscriptions, and propagation bookkeeping. Because it is SYS-owned and undocumented in the public AQ API reference, it is intended solely for consumption by Oracle's own code.

Key Procedures and Functions

The ETRM metadata records the package as VALID with zero documented procedures or functions exposed at the EBS layer. This is expected: DBMS_PRVTAQIS is a private implementation package, and Oracle does not publish its callable specification. Its entry points are invoked exclusively by sibling AQ packages rather than by application code. All behavior is therefore exercised indirectly through the public interfaces of DBMS_AQADM, DBMS_AQ, and DBMS_AQJMS, which delegate internal work to this private layer.

No parameter lists, procedure names, or function signatures are documented for this object. Consultants should not attempt to call members of DBMS_PRVTAQIS directly.

Tables Accessed

According to the documented dependency information, DBMS_PRVTAQIS references SYS.AQ$_AGENT, the dictionary view over the queue agent/subscriber registry. This means the package reads and maintains agent and subscriber metadata used during enqueue and dequeue processing and during propagation scheduling.

No EBS application tables are recorded as accessed through APPS synonyms. The package operates entirely within the SYS-owned AQ data dictionary and the system-managed queue tables created by DBMS_AQADM. In an EBS context, those underlying queue tables include the Workflow Business Event System queues (for example WF_BPEL_Q and related system queues) that are created and administered through AQ.

Usage Notes

DBMS_PRVTAQIS is never invoked directly from Oracle EBS forms, concurrent programs, or customer-written PL/SQL. It is called internally by the following packages, as confirmed by the ETRM dependency listing: DBMS_AQADM_SYS, DBMS_AQJMS, DBMS_AQ_IMPORT_INTERNAL, DBMS_AQ_SYS_IMP_INTERNAL, DBMS_PRVTAQIM, and itself.

  • DBMS_AQADM_SYS — administrative queue operations: create, alter, start, stop, and drop queues and queue tables.
  • DBMS_AQJMS — the AQ JMS administrative and messaging layer.
  • DBMS_AQ_IMPORT_INTERNAL and DBMS_AQ_SYS_IMPORT_INTERNAL — import and metadata reconstruction operations.
  • DBMS_PRVTAQIM — the private AQ propagation and Internet messaging implementation.

In practice, an EBS administrator or developer triggers this package whenever they run scripts or concurrent programs that call DBMS_AQADM or DBMS_AQ, or whenever the Business Event System performs queue administration, agent registration, or event propagation. The practical implication for EBS support is that the package must remain VALID in the SYS schema at all times. If it becomes INVALID — typically after a database upgrade, patch application, or AQ component reinstallation — AQ administration and Business Event propagation will fail. The remedy is to recompile the package body using standard SYS privileges or to run the AQ component scripts supplied with the database release. Because the object is Oracle proprietary and confidential, it should never be modified, wrapped, or reversed.