Search Results drop_object

Overview

AD_ZD_PARALLEL_EXEC is a VALID PL/SQL package owned by the APPS schema in Oracle E-Business Suite. The "AD_ZD" prefix places it within the Oracle Applications Online Patching (ADZD / Edition-Based Redefinition) infrastructure introduced with EBS 12.2, whose architecture is shared across the 12.1.1 to 12.2.2 upgrade path since online patching is a 12.2 feature set. The package provides the parallel execution engine used during the apply and finalize phases of the online patching cycle. Its business function is to coordinate the parallel execution of patching jobs across multiple worker processes, track job status, identify failures, recompile invalid objects, and perform cleanup of temporary DDL handler artifacts. Rather than executing patch operations serially, AD_ZD_PARALLEL_EXEC enables the ADZD framework to distribute work so that the prepare, apply, and cleanup phases complete within the reduced downtime windows that online patching is designed to achieve. As an internal framework package it is not part of the public developer API, but it is central to the reliability of the overall patch cycle.

Key Procedures and Functions

• EXECUTE — The primary entry point that drives the parallel execution of a scheduled set of patching jobs.
• LOAD — Loads the job definitions or work units into the execution framework for processing.
• CLEANUP — Removes residual execution artifacts and temporary state after jobs complete or abort.
• GETFAILED_JOBS — Retrieves jobs that terminated with errors so that the framework can report or retry them.
• GET_NOT_EXECUTED_JOBS — Returns jobs that were queued but never run, supporting resumption of interrupted runs.
• UPDATEJOB_STATUS — Updates the recorded status of a job as it transitions through the execution lifecycle.
• UPDATE_STATUS_R_TO_N — Performs a status transition, mapping a "running" state to a "not started" (or reset) state for retry scenarios.
• RECOMPILE_OBJECTS — Recompiles invalid database objects produced during patching so they become valid and usable.
• GET_ERROR_LEVEL — Returns the current error severity level used to decide whether execution should continue or halt.
• GET_PHASE_ORDER — Returns the ordering of phases that governs the sequence in which work is dispatched.

Tables Accessed

• AD_ZD_DDL_HANDLER and AD_ZD_DDL_HANDLER_DDL_S — Core ADZD routing tables for DDL operations and their associated DDL statements, read/written as jobs are dispatched and their status tracked.
• DBA_INVALID_OBJECTS — Queried by RECOMPILE_OBJECTS to identify invalid objects requiring recompilation after patch application.
• DBMS_APPLICATION_INFO — Used to set module/action context so parallel worker activity is traceable in the database session.
• DBMS_LOB — Used to manipulate large object payloads associated with DDL and job records.
• DBMS_SQL — Provides dynamic SQL execution for applying the generated DDL statements.
• DUAL — Standard single-row utility table for scalar queries and status checks.

Usage Notes

AD_ZD_PARALLEL_EXEC is invoked internally by the ADZD online patching framework rather than through an end-user form or directly submitted concurrent program. It is referenced by five other packages, including AD_ZD, AD_ZD_MVIEW, AD_ZD_PREP, AD_ZD_SEED, and AD_ZD_TABLE, which confirms its role as a shared execution utility across the ADZD family. In practice it is driven during the apply and finalize phases of adop (the AD Online Patching utility), where the framework calls EXECUTE and LOAD to run worker jobs in parallel, periodically checks GETFAILED_JOBS and GET_NOT_EXECUTED_JOBS, and finally invokes CLEANUP. Custom code should not call this package directly; developers extending patching behavior should use the documented ADZD APIs. Because the package depends on SYS.STANDARD and relies on DBMS_SQL, DBMS_LOB, and DBMS_APPLICATION_INFO, it inherits the standard privileges and dynamic-SQL considerations of the APPS schema. Its status is VALID and its components are marked as Oracle Proprietary, Confidential Information.