Search Results load_comprising_patch




Overview
Explore in AI Chat

Overview

AD_PATCH_HIST_MIGR_PKG is a legacy Oracle E-Business Suite database package owned by the APPS schema. Its name and the header comment embedded in the source ("adphmigs.pls", last revised in 2002) indicate that it originally served as a migration utility for loading patch history records into the AD patch driver and patch run repository. During the transition from the Rapid Install / ARU (Automated Release Update) patching model toward the unified AD patch driver architecture, this package provided the extraction-and-load routines required to populate the underlying AD tables from externally sourced data streams. In Oracle EBS 12.1.1 and 12.2.2, the package remains present in the shipped APPS schema and is classified as an OTHER API, meaning it is not part of Oracle's documented public API surface and is intended for internal use by the patching infrastructure rather than direct invocation by customers. The parameter name p_src_cd (source code) and p_exported_from_db throughout the procedures reflect its role in importing patch metadata from an external repository, typically an ARU patch bundle or a patch history export from another environment.

Key Procedures and Functions

The package exposes six documented procedures, each targeting a specific type of patch history record:

  • LOAD_PATCH_DRIVER — Loads a full patch driver record with the complete set of attributes needed to register a driver file, including checksum, file size, driver file name, patch type flags, platform and platform version, original patch name, merge date and merged-driver flag, and the associated application patch identifiers and metadata.
  • LOAD_PATCH_DRIVER_MINIPK — Loads a mini-package driver record, capturing source code, checksum, file size, driver file name, application short name, and patch level. These records represent the smaller driver files associated with individual mini-packs.
  • LOAD_PATCH_DRIVER_LANG — Loads the language-specific driver record, associating a driver file with a particular language code along with its checksum, file size, and source patch driver identifier.
  • LOAD_COMPRISING_PATCH — Loads a comprising patch record, capturing the bug number and ARU release name. This procedure is the one referenced by the search term "load_comprising_patch" and is responsible for recording the relationship between a parent patch and the individual patches that comprise it.
  • LOAD_PATCH_RUN — Loads a patch run record, capturing the execution metadata for a patch application, including start and end dates, application top, patch driver identifier, version numbers, cache flags, and RAPID install flag.
  • UPDATE_CURRENT_VIEW_SNAPSHOT — Refreshes the current-view snapshot used by the patch history reporting layer, ensuring that queries against the _S (snapshot) tables reflect the newly loaded records.

Tables Accessed

The package reads and writes a set of base and snapshot tables in the AD schema, accessed through APPS synonyms. The base tables include AD_APPLIED_PATCHES, AD_APPL_TOPS, AD_BUGS, AD_COMPRISING_PATCHES, AD_PATCH_DRIVERS, AD_PATCH_DRIVER_LANGS, AD_PATCH_DRIVER_MINIPKS, AD_PATCH_RUNS, and the staging table AD_PTCH_HST_EXE_COP_TMP. Each base table has a corresponding "_S" snapshot table (for example AD_PATCH_DRIVERS_S and AD_COMPRISING_PATCHES_S) that mirrors the base data for reporting and restore purposes. The procedures load data into the base tables, while UPDATE_CURRENT_VIEW_SNAPSHOT is responsible for pushing that data into the snapshot tables. AD_PTCH_HST_EXE_COP_TMP acts as the transient staging area from which the load procedures read before inserting into the target repository tables.

Usage Notes

AD_PATCH_HIST_MIGR_PKG is not a public API and is not referenced by any other documented package in the ETRM inventory. It is invoked indirectly by the Oracle patch history migration infrastructure, typically during patch history imports or environment synchronization operations, and may be called from concurrent programs or internal AD utilities. Because it is classified as OTHER and is not referenced by other packages, direct invocation by custom code is strongly discouraged; the parameter lists are undocumented in the ETRM and the data contracts are intended solely for Oracle-internal consumers. Customers performing patch history migrations or cloning operations that require rehydration of the AD patch repository should use the supported AD administration utilities rather than calling these procedures directly. The presence of the package in both 12.1.1 and 12.2.2 reflects continuity of the underlying patch repository schema across those releases.