Results for “logon_trigger_status”

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

Overview

AD_ZD is the core Online Patching (adop) infrastructure package in Oracle E-Business Suite, owned by the APPS schema and delivered in a VALID state in both 12.1.1 and 12.2.2. Its principal business function is to manage the Edition-Based Redefinition (EBR) framework that underpins the Online Patching architecture introduced in Release 12.2. The package provides the runtime and administrative primitives that create, prepare, finalize, and retire database editions, and that control the logon trigger which steers a session into the correct edition during a patch cycle. Because Online Patching depends on editions, AD_ZD effectively governs whether the application tier connects to the "run" (production) edition or the "patch" edition while patching is in progress. In 12.1.1 the package exists but the EBR features it manages are not activated, since Online Patching is not available on that release.

Key Procedures and Functions

The package exposes 25 documented procedures and functions covering three functional areas:

• Diagnostics and logging: LOG and ERROR record messages to the AD_ZD_LOG table; EXEC runs a dynamic SQL statement; LOAD_DDL loads DDL for an object.
• Edition and schema utilities: APPS_SCHEMA and APPLSYS_SCHEMA return the schema names; IS_EDITIONS_ENABLED reports whether EBR is active; GET_EDITION and GET_EDITION_TYPE return the current edition and its type; CHECK_SPACE validates tablespace capacity; SET_EDITION switches the session edition.
• Edition lifecycle and session control: CREATE_EDITION, RETIRE_EDITION, DROP_EDITION, and DROP_OLD_EDITIONS manage the edition hierarchy; ALTER_LOGON_TRIGGER and LOGON_TRIGGER_STATUS manage the logon trigger that assigns editions; KILL_SESSIONS terminates blocking sessions; PREPARE and FINALIZE are the two master entry points invoked at the start and end of an Online Patching cycle to put the system into and out of patch mode.

Parameter lists are not documented in the ETRM metadata; only the named entry points and their roles are recorded.

Tables Accessed

AD_ZD reads and writes its own supporting objects in the APPS schema — AD_ZD_LOG, AD_ZD_MVIEW, AD_ZD_PARALLEL_EXEC, AD_ZD_SEED, and AD_ZD_TABLE. It relies on dynamic performance and dictionary views through APPS synonyms, including DBA_EDITIONS, ALL_EDITIONS, DATABASE_PROPERTIES, DBA_DATA_FILES, DBA_FREE_SPACE, DBA_OBJECTS_AE, DBA_TAB_PRIVS, DBA_TRIGGERS, DBA_USERS, V$PROCESS, and V$SESSION. These are queried to determine edition state, free tablespace, object and trigger status, user and privilege information, and active session counts (used by KILL_SESSIONS). It also depends on SYS.AD_ZD_SYS, FND_ORACLE_USERID, and the DBMS_LOB, DBMS_SESSION, DBMS_SQL, and DBMS_STATS packages.

Usage Notes

AD_ZD is not a public application API. It is invoked internally by the Online Patching tooling (adop and its dependent scripts), by AD utilities such as AutoPatch, and by the AD_ZD-enabled logon trigger during patch cycles. In EBS 12.2.2 it is central to the adop prepare and finalize phases, where PREPARE and FINALIZE orchestrate edition creation, session cleanup, and logon trigger reconfiguration. The package is referenced by 28 other database objects but references none of them in return, confirming its role as an infrastructure foundation layer. Custom developers should not call these procedures directly; they are governed by Oracle-patched internal logic and their behaviour is version-specific.