Search Results ad_zd_logs_s

Overview

AD_ZD_LOG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It forms part of the Online Patching (adzd) infrastructure introduced with the AD Online Patching technology in Release 12.2. Online Patching allows the application of patches to an EBS instance while the system remains available to users, deferring the final cutover step to a scheduled downtime window. Central to that model is the need to record patch-related events in a durable, queryable repository, and AD_ZD_LOG provides the logging interface used by other Online Patching packages to write and manage those records in the AD_ZD_LOGS table.

The object is recorded as VALID and is classified as an OTHER API in the ETRM metadata. Itself a package body, it has no visible specification entry in the documented metadata, but it is referenced by five other database objects, indicating that it is a supporting utility invoked by higher-level Online Patching routines rather than a standalone user-facing API. Its dependency list is narrow, comprising the APPS schema synonyms AD_ZD_LOGS, AD_ZD_LOGS_S, and FND_ORACLE_USERID, plus standard SYS constructs.

Key Procedures and Functions

The documented metadata for AD_ZD_LOG identifies two procedures:

• MESSAGE — The primary logging routine. It writes a message entry into the AD_ZD_LOGS table so that Online Patching activity can be traced and diagnosed. Other Online Patching packages call MESSAGE to record informational, warning, or error output during patch execution and cutover processing.
• CLEAR — A housekeeping routine used to remove or reset log entries maintained by the package. It allows the log store to be cleared, typically before or between patching runs, so that the AD_ZD_LOGS table does not accumulate stale records indefinitely.

Because the metadata does not expose parameter lists, the exact calling signatures are not documented here. No additional procedures or functions are listed for this package body beyond these two, and no parameter details should be assumed.

Tables Accessed

AD_ZD_LOG interacts with the following tables, accessed through APPS synonyms:

• AD_ZD_LOGS — The core log table. MESSAGE inserts rows into this table, and CLEAR deletes from it. This is the persistent store for Online Patching log output.
• AD_ZD_LOGS_S — The sequence associated with AD_ZD_LOGS (the "_S" suffix denotes a sequence object in EBS naming conventions). It supplies the primary key values assigned to newly inserted log rows. The user search term "ad_zd_logs_s" corresponds directly to this sequence, which is the object most commonly queried when investigating how log entries are keyed.
• FND_ORACLE_USERID — The Oracle Applications user identifier table. It is referenced to resolve or validate the database user identity associated with a logged action, attributing each log entry to the correct Oracle user context.

Usage Notes

AD_ZD_LOG is invoked indirectly rather than by end users. It is called by other Online Patching packages during patch application, the prepare and cutover phases of online patching, and related administrative operations. Because it is not referenced by any database object in the dependency listing but does reference tables directly, it functions as a leaf-level logging utility within the adzd package hierarchy.

Custom code and diagnostic scripts do not normally call AD_ZD_LOG directly. Instead, DBAs and developers query the AD_ZD_LOGS table (often filtered by sequence values generated through AD_ZD_LOGS_S) to review patch history and troubleshoot failures. The CLEAR procedure is used to purge accumulated entries. No direct Forms or concurrent program invocation is documented. References to this package should be treated as internal Online Patching infrastructure specific to EBS 12.2.x; it is not present in Release 12.1.1, where the adzd Online Patching framework did not yet exist.