Results for “ad_bugs”

50+ results




Overview
Explore in AI Chat

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

Overview

AD_BUGS is a core Applications DBA (AD) repository table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Oracle Applications bugs fixed," identifying it as the master registry of bug fixes and patch-related defects that Oracle tracks against an EBS environment. In practice, AD_BUGS functions as the authoritative reference for bug numbers that Oracle ships as part of its delivered fixes, and it is central to the AutoPatch and patch-history infrastructure. Because patch application and patching history processing in AD depend on a stable, deduplicated list of bug identifiers, AD_BUGS is referenced repeatedly by patch, snapshot, and patch-run tables throughout the APPLSYS schema.

The table carries a Primary Key constraint, AD_BUGS_PK, defined on BUG_ID, and the documented structure includes 12 columns. From a data-modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning. That is, BUG_ID behaves as a durable business key that anchors references from multiple dependent (link-like or satellite-like) objects, which supports treating AD_BUGS as a hub in a dimensional or Data Vault representation of patching metadata.

Key Information Stored

AD_BUGS is comparatively narrow, and its most significant columns are:

  • BUG_ID — The surrogate primary key and the column referenced by every foreign key that depends on AD_BUGS. It is also the object of the unique index AD_BUGS_U1.
  • BUG_NUMBER — The human-readable Oracle bug or defect identifier displayed to DBAs and used in patch manifests and release notes. It participates in the composite unique index AD_BUGS_U2 (LANGUAGE, BUG_NUMBER, ARU_RELEASE_NAME, BASELINE_NAME, TRACKABLE_ENTITY_ABBR).
  • APPLICATION_SHORT_NAME — The short name of the EBS application (product) to which the bug fix applies, enabling per-product filtering of fixes.
  • ARU_RELEASE_NAME — The ARU (Applications Release Update) release context under which the bug is tracked.
  • BASELINE_NAME — The baseline designation associated with the fix, part of the U2 business-key candidate.
  • TRACKABLE_ENTITY_ABBR — The abbreviated trackable entity used in patch tracking logic, also part of U2.
  • LANGUAGE — The language context of the bug record, included in the composite unique index U2.
  • GENERIC_PATCH — Indicates the generic patch classification of the bug fix.
  • Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY — capture record provenance and modification history.

The two unique indexes are important: AD_BUGS_U1 establishes BUG_ID as the surrogate identifier, while AD_BUGS_U2 defines the composite business-key candidate that distinguishes bug records by language, bug number, release, baseline, and trackable entity.

Common Use Cases and Queries

AD_BUGS is principally queried during patching diagnostics, patch history reporting, and reconciliation of applied fixes. Typical scenarios include identifying which patches delivered a given bug fix, auditing patch runs for a specific defect, and verifying snapshot records created during patching operations.

A representative query joins the bug registry to patch-run data:

  • SELECT b.BUG_NUMBER, b.APPLICATION_SHORT_NAME, p.PATCH_NAME, r.RUN_DATE FROM APPLSYS.AD_BUGS b, APPLSYS.AD_PATCH_RUN_BUGS rb, APPLSYS.AD_PATCH_RUNS r WHERE b.BUG_ID = rb.BUG_ID AND rb.PATCH_RUN_ID = r.PATCH_RUN_ID AND b.BUG_NUMBER = :bug_number;
  • Reporting which baseline and release a bug belongs to using the U2 key columns: SELECT BUG_NUMBER, ARU_RELEASE_NAME, BASELINE_NAME FROM APPLSYS.AD_BUGS WHERE LANGUAGE = 'US' AND TRACKABLE_ENTITY_ABBR = :entity;
  • Correlating snapshot fix records for audit: joining AD_SNAPSHOT_BUGFIXES.BUGFIX_ID to AD_BUGS.BUG_ID.
  • Inventory analysis counting bugs per application: SELECT APPLICATION_SHORT_NAME, COUNT(*) FROM APPLSYS.AD_BUGS GROUP BY APPLICATION_SHORT_NAME;

These patterns are frequently used by DBAs after applying a patch or during upgrade validation in 12.1.1 and 12.2.2.

Related Objects

AD_BUGS is referenced by several dependent AD objects through BUG_ID, which confirms its role as a hub:

  • AD_COMPRISING_PATCHES — Contains AD_COMPRISING_PATCHES.BUG_ID referencing AD_BUGS, linking bugs to the patches that include them.
  • AD_PATCH_RUN_BUGS — Contains AD_PATCH_RUN_BUGS.BUG_ID referencing AD_BUGS, recording bugs associated with each patch run.
  • AD_SNAPSHOT_BUGFIXES — Contains AD_SNAPSHOT_BUGFIXES.BUGFIX_ID referencing AD_BUGS, capturing bug-fix state at snapshot time.
  • AD_PATCH_HIST_TEMP — Temporary patch-history staging table with AD_PATCH_HIST_TEMP.BUG_ID referencing AD_BUGS.
  • AD_PATCH_HIST_SNAPS_TEMP — Snapshot-history staging table with AD_PATCH_HIST_SNAPS_TEMP.BUG_ID referencing AD_BUGS.

Together these relationships position AD_BUGS as the central bug-identity reference consumed by patch application, patch history, and snapshot processes across the APPLSYS patching subsystem.