Search Results ad_zd_log

Overview

AD_ZD_LOG is an Oracle E-Business Suite PL/SQL logging utility owned by the APPS schema and defined with AUTHID CURRENT_USER. Its purpose is to provide a standardized mechanism for capturing diagnostic and status messages emitted by Oracle EBS Online Patching (Edition-Based Redefinition) infrastructure and related AD utilities. The package header carries the revision identifier $Header: ADZDLOGS.pls 120.6 2011/11/15 19:54:44 jpfennin ship $, confirming its role in the AD patching toolchain that was introduced to support online patching in EBS 12.2. In the ETRM classification it is designated as API classification OTHER, reflecting that it is an internal infrastructure package rather than a published business API.

The package writes log records into the AD_ZD_LOG table (referenced through the APPS synonym AD_ZD_LOGS) so that administrators and support engineers can trace the execution of patch-related operations, including edition creation, patch application, and cleanup phases. It is a low-level building block invoked by higher-level AD patching code rather than by end users directly.

Key Procedures and Functions

• MESSAGE — Records a single log entry. Per the inline header comments, the procedure accepts a module identifier, a log type, and the message text, and inserts the resulting record into the AD_ZD_LOG table. The documented log type values are STATEMENT (useful or detailed diagnostic information), PROCEDURE (marking the beginning or end of a procedure), EVENT (a normal, expected occurrence), and ERROR (a failure or abnormal condition). These four levels allow callers to filter or interpret log output according to severity and context.
• CLEAR — Truncates the AD_ZD_LOG table, removing all previously accumulated log rows. This is typically used at the start of a patching session or maintenance window to reset the log so that subsequent operations can be analyzed in isolation.

The package exposes only these two documented procedures. No functions are declared in the published header.

Tables Accessed

• AD_ZD_LOGS — The primary log table, accessed through its APPS synonym. MESSAGE inserts log rows here, and CLEAR truncates it.
• AD_ZD_LOGS_S — The sequence associated with the log table, used to generate unique log identifiers for each inserted row.
• FND_ORACLE_USERID — Referenced to resolve or record the Oracle user identity associated with log entries, providing an audit trail of which database user performed a logged operation.

All table references are made through APPS synonyms, consistent with the package's AUTHID CURRENT_USER declaration and its placement in the APPS schema.

Usage Notes

AD_ZD_LOG is an internal AD utility. It is invoked programmatically by other AD and online patching packages rather than exposed through a form, concurrent program, or menu function. ETRM records that the package is referenced by five other packages in the 12.2.2 codebase, which is consistent with its role as a shared logging service for the AD patching stack.

Because the package is not a business-facing API, custom code should not depend on its procedures for application logging; Oracle does not guarantee the stability of internal AD interfaces across patch levels. Administrators reviewing online patching activity would instead query the AD_ZD_LOGS table directly, using the log type values described above to isolate errors or to reconstruct the sequence of events during an adop patching cycle. The CLEAR procedure should be treated with caution in any live environment, as truncation is destructive and removes prior diagnostic history that may be required for support investigations.