Search Results load_patch_driver




Overview
Explore in AI Chat

Overview

AD_PATCH_HIST_MIGR_PKG is an Oracle Applications internal PL/SQL package owned by the APPS schema that supports migration and replenishment of the patch history repository maintained by Oracle E-Business Suite's patching infrastructure (AD Patch / AutoPatch). During an upgrade, a database migration, an AD Administration "Maintain Patch Information" cycle, or the propagation of an AutoPatch session from a source environment to a target environment, the patch driver history stored in the AD_PATCH_DRIVERS, AD_PATCH_RUNS, and related tables must be loaded into the destination database. AD_PATCH_HIST_MIGR_PKG provides the packaged interfaces that perform those loads, accepting a full complement of attributes that describe a patch driver record — checksum, file size, driver filename, source code, driver type flags, platform and platform version, original patch name, merge attributes, patch name and type, mini-pack level, and rapid-install flags.

The package is declared AUTHID CURRENT_USER, so all SQL executes with the privileges of the invoking session rather than the package owner. The header revision ($Header: adphmigs.pls 115.6 2002/02/26) indicates this is a long-lived component of the AD product family and is present across both 12.1.1 and 12.2.2 environments, though in 12.2.2 it is invoked largely through the online patching infrastructure rather than user interaction.

Key Procedures and Functions

  • LOAD_PATCH_DRIVER — The primary loader for a full patch driver record. It accepts the complete set of driver attributes (source patch driver identifier, checksum, file size, driver filename, source code, driver type flags for "c", "d", and "g" driver classifications, platform, platform version, original patch name, merge flag and merge date, source applied patch identifier, patch name, patch type, mini-pack level, applied patch source code, exported-from-database indicator, and the rapid-installed flag). This is the procedure most commonly located by searches for "load_patch_driver".
  • LOAD_PATCH_DRIVER_MINIPK — Loads the mini-pack association rows for a patch driver, taking the driver key, checksum, file size, filename, export indicator, application short name, and patch level.
  • LOAD_PATCH_DRIVER_LANG — Loads language-specific rows for a patch driver, taking the driver key and file attributes together with a language code.
  • LOAD_COMPRISING_PATCH — Loads comprising (included) patch relationships, taking the driver key and file attributes plus the bug number and ARU release name for each contained patch.
  • LOAD_PATCH_RUN — Loads an AutoPatch run history record, capturing start and end dates, the AT (AutoPatch) name, the APPL_TOP name, caching flag for application top identifiers, file attributes, source code, associated patch driver identifier, export indicator, the major/minor/tap version triple both as applied and as updated ("upd_to" values), the rapid-install flag, the patch top directory, and the source patch run identifier.
  • UPDATE_CURRENT_VIEW_SNAPSHOT — Refreshes the snapshot view that exposes the current (most recent) patch state, ensuring that the migrated history is visible through the current-history reporting views.

Tables Accessed

The package reads and writes the core patch-history base tables and their _S shadow/seed tables via APPS synonyms: AD_PATCH_DRIVERS and AD_PATCH_DRIVERS_S (driver definitions), AD_PATCH_DRIVER_MINIPKS and AD_PATCH_DRIVER_MINIPKS_S (mini-pack mappings), AD_PATCH_DRIVER_LANGS and AD_PATCH_DRIVER_LANGS_S (language rows), AD_PATCH_RUNS and AD_PATCH_RUNS_S (AutoPatch run history), AD_APPLIED_PATCHES and AD_APPLIED_PATCHES_S (applied patch records), AD_COMPRISING_PATCHES and AD_COMPRISING_PATCHES_S (included patch relationships), AD_BUGS (bug number reference data), AD_APPL_TOPS (application top identifiers used by LOAD_PATCH_RUN), and the staging table AD_PTCH_HST_EXE_COP_TMP, which holds patch history during migration or copy operations.

Usage Notes

AD_PATCH_HIST_MIGR_PKG is not intended for direct end-user invocation. It is called by AD utilities — AD Administration, AutoPatch, the patch-history migration routines executed during upgrades to 12.1.1 or 12.2.2, and the transitional adoption of a non-EBS patch history into the EBS repository. No other APPS package is documented as referencing it, so it functions primarily as a service entry point for the AD executables and for the temporary-table-driven migration process. Custom code should not call these procedures directly; supported patch-history maintenance is performed through AD Administration and the standard patching tools. Access to the package and its underlying tables is restricted to the APPS schema and application patching responsibilities.