Results for “alter_logon_trigger”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SYS.AD_ZD_SYS is a core Oracle E-Business Suite database package body that implements the underlying infrastructure of the Edition-Based Redefinition (EBR) framework used by Online Patching. Although it resides in the SYS schema rather than the APPLSYS or APPS schemas, AD_ZD_SYS forms part of the AD (Applications DBA) "ZD" family of packages known collectively as the AD Online Patching / editioning utilities. Its principal business function is to manage the lifecycle of editions and of "covered" (editioned) database objects so that a running EBS 12.2.x environment can be patched while users remain connected, with cutover to the newly patched edition deferred until the sysadmin chooses to do so.

The package operates on the dictionary views that describe editions (ALL_EDITIONS, DBA_EDITIONS), object editioning state (DBA_OBJECTS, DBA_OBJECTS_AE, OBJ$, USER$), privileges (DBA_TAB_PRIVS), and the Oracle-supplied DATABASE_PROPERTIES view. It also references FND_ORACLE_USERID, the EBS repository table that maps application users to Oracle schema accounts, reinforcing its role as the bridge between generic Oracle editioning and EBS-specific identity management.

Key Procedures and Functions

The ETRM documentation for release 12.2.2 records eight public subprograms:

• RETIRE_EDITION — Marks an existing edition as retiring, preparing it for removal once dependent sessions and objects no longer reference it.
• RETIRE_OLD_EDITIONS — Bulk variant of RETIRE_EDITION that scans the edition hierarchy and retires those older editions that are eligible, supporting housekeeping after successive patch cycles.
• DROP_EDITION — Physically removes an edition from the database once it has been retired and is confirmed unreferenced.
• DROP_COVERED_OBJECT — Removes a single covered object (an object that has been editioned as part of the patch) from the current edition.
• DROP_COVERED_OBJECTS — Set-based counterpart that drops multiple covered objects in one invocation, used during cleanup of a completed patch.
• ACTUALIZE_OBJECT — "Actualizes" (materialises) a covered object so that its definition is propagated into the run edition, making the patched version effective for the running application.
• ACTUALIZE_ALL — Applies ACTUALIZE_OBJECT across all eligible covered objects, typically executed as part of the final cutover / "adop phase=cutover" or cleanup processing.
• ALTER_LOGON_TRIGGER — Repoints or toggles the EBS logon trigger so that new sessions attach to the correct (new or old) edition during the patch cycle's switchover window.

Tables Accessed

The package reads Oracle dictionary views rather than application data tables. DBA_EDITIONS and ALL_EDITIONS supply the catalogue of editions and their parent-child relationships. DBA_OBJECTS, DBA_OBJECTS_AE and the base tables OBJ$ and USER$ provide object-level metadata including editioning status and ownership. DBA_TAB_PRIVS is consulted to validate grants made on covered objects, and DBA_DEPENDENCIES supports impact analysis when objects are actualised or dropped. DATABASE_PROPERTIES is used to detect edition-related database configuration, while FND_ORACLE_USERID maps EBS application identities to Oracle schemas so that editioning operations are attributed and restricted correctly.

Usage Notes

AD_ZD_SYS is not intended for direct invocation by end users or by ordinary custom code. It is called internally by higher-level AD utilities — most notably the ADOP (AD Online Patching) driver and its supporting PL/SQL such as AD_ZD, AD_ZD_TABLE, and AD_ZD_VIEW — during the prepare, apply, finalize, cutover, and cleanup phases of an online patch. Administrators effectively exercise its procedures through ADOP command-line operations (for example, adop phase=cutover) and through the Patch Manager / adop console rather than by executing AD_ZD_SYS procedures directly. Because the package resides in SYS and manipulates edition and object metadata, direct execution requires elevated privileges and should be attempted only under Oracle Support guidance. Custom code should never depend on AD_ZD_SYS, as its interface is internal and may change between EBS 12.2.x release updates; it is not referenced by any database object outside the AD editioning framework.