Search Results actualize_all

Overview

SYS.AD_ZD_SYS is the core dictionary-level PL/SQL package that Oracle E-Business Suite uses to manage the Oracle Database Editioning infrastructure introduced with Online Patching in EBS 12.2. Because online patching depends on Edition-Based Redefinition (EBR), an edition must be created for every patch cycle, objects must be redefined in a non-default edition, and superseded editions must eventually be removed. AD_ZD_SYS exposes the low-level operations that perform these actions, and it is declared AUTHID DEFINER, meaning it executes with the privileges of its owner, SYS, rather than the invoker. This is essential, since the procedures manipulate editioned objects and edition metadata that only a privileged schema can touch. The package is part of the AD (Applications DBA) product family and works alongside the higher-level AD_ZD, AD_ZD_* helper packages, and the Online Patching / adop utilities. Its header, derived from adgrants.sql, confirms that it is a shipped, supported dictionary object rather than customer code, and it is classified in the ETRM repository as a package of type OTHER.

Key Procedures and Functions

• RETIRE_EDITION — Retires a single named edition so that it is no longer available for new sessions, typically after its patch cycle has completed and no users remain connected to it.
• RETIRE_OLD_EDITIONS — Retires all editions that are no longer required, providing the bulk cleanup of superseded patch editions.
• DROP_EDITION — Physically drops a specified edition from the database once it has been retired and is safe to remove.
• DROP_COVERED_OBJECT — Drops a single covered (editioned) object identified by owner, object name, and object type from a given edition.
• DROP_COVERED_OBJECTS — Drops all covered objects associated with an edition; the boolean execute flag allows a dry-run or report before the destructive action is committed.
• ACTUALIZE_OBJECT — Actualizes a single object, that is, it makes the object's crossed edition metadata take effect so that the object becomes fully visible in the running edition.
• ACTUALIZE_ALL — Actualizes all eligible objects in the system, completing the transition of the editioned environment after a patch application. This is the procedure most commonly associated with the search term "actualize_all".
• ALTER_LOGON_TRIGGER — Enables or disables the logon trigger that governs which edition a newly connecting session attaches to, thereby controlling the cutover of user traffic between editions.

Tables Accessed

The documented table reference for this package is FND_ORACLE_USERID, accessed through an APPS synonym. This table holds the mapping between Oracle database users and EBS application users, and the package consults it to determine which schemas and connections are relevant when retiring editions, altering the logon trigger, or actualizing objects. Because AD_ZD_SYS is a SYS-owned dictionary package, the bulk of its underlying operations are performed against Oracle data dictionary and EBR views rather than application tables; the FND_ORACLE_USERID reference is the primary documented bridge back to EBS metadata.

Usage Notes

AD_ZD_SYS is not intended for direct invocation by end users or ordinary custom code. It is called by the Online Patching infrastructure — principally by adop and the AD_ZD family of packages — during the cutover, cleanup, and finalize phases of a patch cycle. ACTUALIZE_ALL is invoked to force the editioned state of all objects to be actualized after a patch has been applied and the new edition is to become the default runtime environment. RETIRE_OLD_EDITIONS and DROP_EDITION are invoked during cleanup to reclaim space and remove stale editions. Because the package runs AUTHID DEFINER and manipulates edition metadata, direct execution requires SYSDBA-level privileges and should only be attempted under Oracle Support direction or by an experienced DBA following a documented recovery procedure. One other package in the EBS codebase references AD_ZD_SYS, underlining its role as a low-level dependency rather than a general-purpose API.