Results for “bug_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AD_PATCH_RUN_BUGS is an Oracle Applications DBA (AD) repository table owned by the APPLSYS schema. It records the individual bug fixes associated with a specific execution of AutoPatch, the utility that applies patches, patch sets, and maintenance packs to an Oracle E-Business Suite environment. Each row represents one bug that was either considered, applied, or deliberately skipped during a given patch run, giving DBAs and support analysts an auditable trace of what a patch actually delivered at the bug level rather than merely at the patch level.

The table resides in the maintenance and patching subject area of Oracle EBS and is populated automatically by AutoPatch during patch application. It is available in both 12.1.1 and 12.2.2, where the documented physical schema in APPLSYS contains 13 columns. From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table is anchored by the surrogate key PATCH_RUN_BUG_ID and hangs off parent hub-like entities AD_PATCH_RUNS and AD_BUGS, capturing descriptive outcomes and status attributes about the relationship between a run and a bug.

Key Information Stored

The surrogate primary key is PATCH_RUN_BUG_ID, enforced by the AD_PATCH_RUN_BUGS_PK constraint. Two unique indexes act as business-key candidates: AD_PATCH_RUN_BUGS_U1 on PATCH_RUN_BUG_ID alone, and the more meaningful AD_PATCH_RUN_BUGS_U2 on the composite of PATCH_RUN_ID, BUG_ID, ORIG_BUG_NUMBER, and APPLICATION_SHORT_NAME. The composite uniqueness indicates that the same bug number can legitimately appear under more than one original bug reference or application context within a run.

• PATCH_RUN_ID — Foreign key to AD_PATCH_RUNS, identifying the specific AutoPatch execution that processed this bug.
• BUG_ID — Foreign key to AD_BUGS, identifying the canonical bug record being addressed.
• ORIG_BUG_NUMBER — The original bug number as referenced by the source patch, which may differ from the normalized BUG_ID.
• APPLICATION_SHORT_NAME — The application (product) short name to which the bug fix belongs, such as GL, AP, or INV.
• APPLIED_FLAG — Indicates whether the bug fix was actually applied during the run.
• REASON_NOT_APPLIED — Free-text explanation recorded when a bug was skipped or excluded.
• SUCCESS_FLAG — Indicates whether application of the fix completed successfully.
• FAILURE_COMMENTS — Diagnostic text captured when the fix failed.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns recording who created and last modified the row and when.

Common Use Cases and Queries

DBAs use this table to reconcile what a patch run actually fixed, to investigate failed or skipped fixes, and to verify that a critical bug was applied before promoting an environment. A typical query joins to AD_PATCH_RUNS to frame the run and filters on outcome flags:

• Listing failed fixes for a run: SELECT b.orig_bug_number, b.application_short_name, b.failure_comments FROM ad_patch_run_bugs b WHERE b.patch_run_id = :run_id AND b.success_flag = 'N';
• Finding skipped fixes and the stated reasons: filter on applied_flag = 'N' and select REASON_NOT_APPLIED.
• Tracking whether a specific bug number was applied across recent runs by joining AD_PATCH_RUNS on PATCH_RUN_ID and ordering by the run's start time.
• Product-level reporting on fix volume per APPLICATION_SHORT_NAME for capacity or regression analysis.

These queries support release readiness checks, post-patch validation, and audit evidence collection for change management.

Related Objects

The table participates in a well-defined network of AD patching objects. Its parent references are AD_PATCH_RUNS (via PATCH_RUN_ID) and AD_BUGS (via BUG_ID). Dependent children that reference this table include AD_PATCH_RUN_BUG_ACTIONS (via PATCH_RUN_BUG_ID), which records the individual actions performed for each bug in a run, and AD_PATCH_HIST_TEMP (via PATCH_RUN_BUG_ID), a staging object used in patch history processing. Together with AD_PATCH_RUNS, AD_BUGS, AD_PATCH_RUN_BUG_ACTIONS, AD_PATCH_HIST_TEMP, and the AD_PATCH_RUN_BUGS_PK and AD_PATCH_RUN_BUGS_U2 constraints, these objects form the core of bug-level patch traceability in Oracle EBS 12.1.1 and 12.2.2.