Search Results update_current_view_snapshot




Overview
Explore in AI Chat

Overview

AD_PATCH_HIST_MIGR_PKG is an internal Oracle Applications (APPS) PL/SQL package responsible for migrating and loading patch history metadata into the AD patch-related repository tables within the Oracle E-Business Suite database. Its central role is to populate the seed and staging structures that record which patches, patch drivers, comprising patches, mini-packages, and language-specific driver files have been applied to an EBS instance. The package is defined AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is consistent with its use inside the patching infrastructure (AD utilities) where the calling process operates as the APPLSYS/APPS schema owner.

In the context of EBS 12.1.1 and 12.2.2, this package belongs to the patching subsystem (the "AD" namespace) and supports data movement from externally exported patch histories — for example, histories exported from another database — into the local AD dictionary tables. This enables clone, migration, and synchronization scenarios where an administrator must reconcile or transfer patch history between environments without re-applying every patch. The package is not intended for direct end-user or customer invocation; it is a supporting utility referenced by the patching framework.

Key Procedures and Functions

The ETRM metadata documents six procedures within this package. Descriptions below reflect documented purpose only; parameter lists are not reproduced.

  • LOAD_PATCH_DRIVER — Loads a full patch driver record, capturing driver identification, checksum, file size, file name, source code, driver type flags (comprising, dependency, generic), platform and platform version, original patch name, merge information, and associated application patch attributes such as patch name, type, mini-pack level, and rapid-install flag. This is the primary routine for reconstructing driver-level patch history.
  • LOAD_PATCH_DRIVER_MINIPK — Loads mini-package driver records, associating a source code, checksum, file size, file name, source patch driver identifier, export source, application short name, and patch level.
  • LOAD_PATCH_DRIVER_LANG — Loads language-specific patch driver records, capturing the language in addition to the standard source, checksum, file size, file name, and source driver identifier.
  • LOAD_COMPRISING_PATCH — Loads records for patches that are comprised within a parent patch (comprising patches), including the bug number and ARU release name associated with each comprising patch.
  • LOAD_PATCH_RUN — The procedure most relevant to the search term "load_patch_run." It loads a patch run record, capturing run timing (start and end dates), application and system names, caching flags, checksum, file name and source, the associated patch driver identifier, export source, versioning information (major, minor, and tap versions, both source and "updated to" values), the returned patch run identifier, and the rapid-install flag.
  • UPDATE_CURRENT_VIEW_SNAPSHOT — Refreshes the current-view snapshot associated with the migrated patch history, ensuring the runtime views reflect the newly loaded records.

Tables Accessed

The package reads and writes the following documented tables (referenced through APPS synonyms):

The consistent "_S" suffix tables indicate that the package maintains snapshot (history) copies alongside current-view tables, which is a standard AD architectural pattern for preserving patch history while presenting a current working view.

Usage Notes

AD_PATCH_HIST_MIGR_PKG is an internal infrastructure package and is not exposed through standard EBS forms or documented concurrent programs for direct customer use. It is invoked by the AD patching utilities — typically during operations that migrate or seed patch history, such as clone preparation, history reconciliation between environments, or the export/import of patch metadata. In 12.1.1 and 12.2.2 these operations are coordinated by the AutoPatch and AD administration tooling under the APPLSYS/APPS schema.

Because the package is declared AUTHID CURRENT_USER, executing it requires that the invoking session hold appropriate privileges on the underlying AD tables. Custom code, DBA scripts, or third-party tooling should not call these procedures directly; doing so risks corrupting patch history and snapshot integrity. When patch history must be manipulated or queried by administrators, the supported approach is to use the sanctioned AD utilities and diagnostic scripts rather than invoking this package's procedures. The metadata records zero dependent packages, indicating it is a leaf utility relied upon by the patching framework rather than a shared API.