Search Results ad_patch_runs




Overview
Explore in AI Chat

Overview

The AD_PATCH_RUNS table is a core repository for high-level patching history within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Owned by the APPLSYS schema and part of the Applications DBA (AD) product module, it serves as the primary audit log for Autopatch operations. As its description states, it records one row for each patch driver file applied to the system, providing a centralized, chronological record of all patching activities. This table is fundamental for tracking the evolution of an EBS instance, enabling administrators to verify patch application, understand the system's patching sequence, and troubleshoot deployment issues.

Key Information Stored

The table's structure is designed to capture essential metadata about each patch run. Its primary key, PATCH_RUN_ID, uniquely identifies each driver application. Critical foreign key relationships provide context: PATCH_DRIVER_ID links to AD_PATCH_DRIVERS for driver-specific details, while APPL_TOP_ID references AD_APPL_TOPS, identifying the APPL_TOP where the patch was applied. The RELEASE_ID and UPDATED_TO_RELEASE_ID columns, both referencing AD_RELEASES, document the system's release state before and after the patch run, which is vital for tracking release updates. While specific column names beyond the keys are not detailed in the provided metadata, typical data stored includes timestamps for the start and end of the run, the execution status, the name of the applied driver, and the invoking user.

Common Use Cases and Queries

The primary use case is generating patching history reports for audit and compliance. Database administrators frequently query this table to list all applied patches, determine the last patch applied, or investigate failed patching sessions. A common query retrieves a chronological summary of patch runs:

  • SELECT patch_run_id, driver_file_name, start_time, end_time, status FROM applsys.ad_patch_runs ORDER BY start_time DESC;

Another critical scenario involves correlating a patch run with the specific bugs it fixed by joining with the AD_PATCH_RUN_BUGS table. This is essential for validating that a particular bug fix or mandatory patch has been successfully implemented in the environment. Troubleshooting often involves examining runs with a failed or warning status to identify problematic patching cycles.

Related Objects

AD_PATCH_RUNS is a central node in the patching data model. It has direct foreign key relationships with several key tables: AD_PATCH_DRIVERS (details of the driver file), AD_APPL_TOPS (the target application tier), and AD_RELEASES (release identifiers). Most importantly, it has a one-to-many relationship with the AD_PATCH_RUN_BUGS table, which lists every bug fixed in a given patch run. This relationship is crucial for detailed patch reporting. The table is also referenced by various internal Oracle Applications Manager (OAM) views and patching utilities that provide a user-friendly interface to the underlying patching history data stored in AD_PATCH_RUNS.