Results for “ad_snapshot_bugfixes”

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

Overview

AD_SNAPSHOT_BUGFIXES is a transactional table owned by the APPLSYS schema within the Applications DBA (AD) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the bug fixes that were applied to an E-Business Suite environment at the moment an AD snapshot was captured. Because AD snapshots are used to preserve the state of an application system for diagnostic, support, and rollback purposes, this table provides the audit trail that ties a specific snapshot image to the set of Oracle patches and bug fixes present in that image.

Under a heuristic Data Vault classification mined from its foreign key structure, the table may be modeled as a link entity. It resolves a many-to-many association between snapshots (AD_SNAPSHOTS) and bug fixes (AD_BUGS), and it carries descriptive attributes (status flags and timestamps) that a pure junction table would not typically require. This dual nature makes it useful both as a relationship bridge and as a lightweight satellite of patch application history.

Key Information Stored

The table contains ten documented columns. The most important are summarized below.

• SNAPSHOT_BUG_ID — the surrogate primary key, enforced by index AD_SNAPSHOT_BUGFIXES_PK. It uniquely identifies each row.
• SNAPSHOT_ID — foreign key to AD_SNAPSHOTS, identifying the snapshot under which the bug fix was recorded.
• BUGFIX_ID — foreign key to AD_BUGS, identifying the specific bug fix or patch applied.
• BUG_STATUS — the status of the associated bug fix at snapshot time (for example, applied, pending, or failed).
• SUCCESS_FLAG — indicates whether the bug fix was successfully applied.
• INCONSISTENT_FLAG — flags a snapshot entry whose recorded bug-fix state does not reconcile with the live dictionary, useful during snapshot validation.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns recording who created and last modified the row.

Two unique indexes document the business-key candidates: AD_SNAPSHOT_BUGFIXES_U1 on SNAPSHOT_BUG_ID and AD_SNAPSHOT_BUGFIXES_U2 on the composite (BUGFIX_ID, SNAPSHOT_ID). The composite uniqueness guarantees that any given bug fix appears at most once per snapshot, which is the natural business rule for this entity.

Common Use Cases and Queries

DBAs and support engineers query this table when comparing the patch level of two snapshots, when auditing which fixes were present at a point in time, or when diagnosing patch-related failures reproduced from a snapshot.

• List all bug fixes captured in a given snapshot:

  SELECT b.BUG_NUMBER, s.BUG_STATUS, s.SUCCESS_FLAG
FROM AD_SNAPSHOT_BUGFIXES s, AD_BUGS b
WHERE s.BUGFIX_ID = b.BUG_ID
AND s.SNAPSHOT_ID = :snapshot_id;

• Identify snapshots where a specific fix was applied:

  SELECT SNAPSHOT_ID FROM AD_SNAPSHOT_BUGFIXES WHERE BUGFIX_ID = :bug_id;

• Detect inconsistencies requiring investigation:

  SELECT * FROM AD_SNAPSHOT_BUGFIXES WHERE INCONSISTENT_FLAG = 'Y';

• Report unresolved or failed fixes within a snapshot using BUG_STATUS and SUCCESS_FLAG.

Related Objects

The following objects are most closely associated with AD_SNAPSHOT_BUGFIXES through its documented constraints and usage.

• AD_SNAPSHOTS — parent table; joined via SNAPSHOT_ID. Provides snapshot metadata such as creation time and type.
• AD_BUGS — reference table; joined via BUGFIX_ID. Supplies bug numbers, descriptions, and patch information.
• AD_SNAPSHOT_BUGFIXES_PK, AD_SNAPSHOT_BUGFIXES_U1, AD_SNAPSHOT_BUGFIXES_U2 — the primary key and unique indexes enforcing row and business-key integrity.
• AD_SNAPSHOT_OBJECTS and other AD_SNAPSHOT_* tables — sibling tables describing the broader snapshot content and used together in snapshot comparison reports.