Search Results ad_patch_run_bugs




Overview
Explore in AI Chat

Overview

The APPLSYS.AD_PATCH_RUN_BUGS table is a core repository table within the Oracle E-Business Suite Applications DBA (AD) module. It serves as a transactional junction table that records the specific bugs addressed during each execution of the Autopatch utility (AD Patch, or ADPATCH). This table is fundamental to the patching infrastructure, creating an auditable link between a patch run, identified in AD_PATCH_RUNS, and the individual software bugs, defined in AD_BUGS, that the run was intended to resolve. Its existence enables precise tracking, reporting, and dependency analysis of applied fixes across the EBS environment, which is critical for maintenance, compliance, and troubleshooting.

Key Information Stored

The table's primary purpose is to associate a Bug ID with a Patch Run ID. Its structure is defined by this relationship and its unique identifier. The most critical columns include:

  • PATCH_RUN_BUG_ID: The primary key (PK) column, a unique system-generated identifier for each record linking a bug to a run.
  • PATCH_RUN_ID: A foreign key (FK) column referencing the AD_PATCH_RUNS table. This identifies the specific Autopatch session.
  • BUG_ID: A foreign key column referencing the AD_BUGS table. This identifies the specific Oracle bug number that was fixed.

These columns form the essential data model, allowing the system to answer which bugs were fixed in a given patch run and, conversely, which patch runs applied a particular bug fix.

Common Use Cases and Queries

This table is primarily queried for patch analysis and audit reporting. Common scenarios include generating a report of all bugs fixed during a recent patching cycle, verifying if a specific critical bug fix has been applied, and investigating patch run details. A typical query joins to AD_PATCH_RUNS for run details (like timing and driver file) and to AD_BUGS for bug descriptions.

Sample Query: List bugs fixed in a specific patch run.
SELECT prb.patch_run_bug_id, b.bug_number, b.description
FROM applsys.ad_patch_run_bugs prb,
applsys.ad_bugs b,
applsys.ad_patch_runs pr
WHERE prb.bug_id = b.bug_id
AND prb.patch_run_id = pr.patch_run_id
AND pr.patch_run_id = &your_run_id;

Sample Query: Find which patch run applied a particular bug fix.
SELECT pr.patch_run_id, pr.run_start_date
FROM applsys.ad_patch_run_bugs prb,
applsys.ad_patch_runs pr,
applsys.ad_bugs b
WHERE prb.patch_run_id = pr.patch_run_id
AND prb.bug_id = b.bug_id
AND b.bug_number = '12345678';

Related Objects

AD_PATCH_RUN_BUGS is centrally connected within the AD patching schema, as documented in the provided metadata.

  • Parent Tables (Referenced by Foreign Keys):
    • AD_PATCH_RUNS: Joined via AD_PATCH_RUN_BUGS.PATCH_RUN_ID = AD_PATCH_RUNS.PATCH_RUN_ID. Provides execution context for the bug fix.
    • AD_BUGS: Joined via AD_PATCH_RUN_BUGS.BUG_ID = AD_BUGS.BUG_ID. Provides details about the bug itself.
  • Child Table (References this table via Foreign Key):
    • AD_PATCH_RUN_BUG_ACTIONS: Joined via AD_PATCH_RUN_BUG_ACTIONS.PATCH_RUN_BUG_ID = AD_PATCH_RUN_BUGS.PATCH_RUN_BUG_ID. This table likely records the specific file or database object actions (e.g., SQL, EXEC, JAR) taken to resolve the bug within the patch run.