Search Results adop_patch_apply_status

Overview

AD_ZD_ADOP is a PL/SQL package owned by the APPS schema that serves as the primary programmatic engine for Oracle's Online Patching (also known as ADOP — the Automated Patching utility) in Oracle E-Business Suite Release 12.2. In the 12.2 architecture, the file system and database are split into a "run" edition and a "patch" edition, enabling applications to remain available while patches are applied. AD_ZD_ADOP orchestrates the lifecycle of this process, managing patch sessions, coordinating snapshot flips, controlling the cutover between editions, and tracking patch run history. The package is classified as an "OTHER" API in the ETRM metadata, indicating that it is an internal infrastructure component rather than a general-purpose business API exposed for customer extension. It is central to the ADOP (adop) command-line utility, translating operator commands into database operations that drive the online patching cycle.

Key Procedures and Functions

The package exposes 28 documented procedures and functions, grouped here by purpose:

• Patch and session management: SUBMIT_REQUEST, GET_ACTIVE_CP_REQUEST_ID, INSERT_INTO_PATCHES_TABLE, and INSERT_CLONE_TRACKING_ROW manage the creation and tracking of ADOP patch runs, including concurrent request submission and clone tracking.
• Status retrieval: ADOP_PATCH_APPLY_STATUS, GET_CUTOVER_STATUS, GET_ADZDPATCH_STATUS, and GETPATCHNUMBERS report the current state of a patch cycle, cutover progress, and patch identification.
• Cutover and edition management: CUTOVER, FLIP_SNAPSHOTS, WAIT_FOR_DB_CUTOVER, and WAIT_FOR_CP_TO_RUN coordinate the transition from the run edition to the patch edition, including the snapshot flip that makes patched code live and synchronizing concurrent processing.
• Session control: KILL_OLD_SESSIONS, LOCK_SESSIONS_TABLE, UNLOCK_SESSIONS_TABLE, LOCK_PATCHES_TABLE, and UNLOCK_PATCHES_TABLE manage active database sessions during cutover and guard against concurrent modification of ADOP control tables.
• Monitoring and safety: IS_ICM_ALIVE verifies the Internal Concurrent Manager is running before critical steps, and SET_CUTOVER_STATUS records cutover state. ABORT terminates an in-progress patch cycle.

Tables Accessed

AD_ZD_ADOP reads from and writes to a defined set of APPS-synonym tables central to ADOP operation:

• AD_ADOP_SESSIONS and AD_ADOP_SESSION_ID_SEQ store and generate the identifiers for each ADOP patch session.
• AD_ADOP_SESSION_PATCHES tracks which patches belong to a given session.
• AD_PATCH_RUNS, AD_PATCH_RUN_BUGS, and AD_PATCH_RUN_BUG_ACTIONS record patch execution history, associated bug numbers, and the actions performed.
• AD_SNAPSHOTS, AD_SNAPSHOT_FILES, AD_SNAPSHOT_FILES_S, and AD_SNAPSHOT_BUGFIXES underpin the snapshot flip mechanism that swaps file system editions during cutover.
• AD_APPL_TOPS, AD_RELEASES, and AD_TE_LEVEL_HISTORY provide application topology, release, and edition-level history used to determine patching context.
• AD_CHECK_FILE_HISTORY and AD_TRACKABLE_ENTITIES support file-change tracking and entity registration during patching.

Usage Notes

AD_ZD_ADOP is invoked primarily by the ADOP command-line utility and its supporting concurrent programs rather than by end users. The adop tool issues calls to this package for actions such as apply, cutover, cleanup, and abort, making it the database-side counterpart to the file-system operations performed by the patch driver. Because it is an internal APPS-owned package, Oracle does not document it as a supported extension API; custom code should not call its procedures directly, as signatures and behavior may change across patch levels and the package is referenced by zero other packages in the ETRM dependency record. Its status is VALID and it depends only on SYS and STANDARD. Administrators and DBAs typically encounter AD_ZD_ADOP indirectly through ADOP logs and the querying of AD_ADOP_SESSIONS and related tables to monitor or troubleshoot online patching cycles.