Results for “bug_number”

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

Overview

AD_PA_ANAL_BUG_DEPS is an Applications DBA (AD) product table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the dependency relationships for bugs that are produced when a Criteria Analysis run is executed by the Patching and Analysis (PA) framework. In practical terms, the table records which prerequisite bug must be applied before a given bug can be considered satisfied for a specific APPL_TOP, thereby allowing the analysis engine to reason about patch ordering and prerequisite chains at the file-system and application-tier level.

The table is registered as VALID in the ETRM metadata and is described as a repository for "the dependencies for bugs resulting from Criteria Analysis run." Its scope is administrative rather than transactional: it supports the diagnostic and prerequisite-evaluation logic used by AD utilities such as adpatch and the online patching infrastructure in 12.2.x. Under the heuristic Data Vault classification supplied in the metadata, AD_PA_ANAL_BUG_DEPS is mined as standalone. This is best read as a modeling suggestion rather than an authoritative classification; because the table carries a composite unique key over ANALYSIS_RUN_ID, BUG_NUMBER, APPL_TOP_ID, and PREREQ_BUG_NUMBER, it could alternatively be modeled as a link table connecting bug and APPL_TOP hubs, with the remaining audit columns treated as satellite attributes. The documented schema shows nine columns.

Key Information Stored

The most important columns fall into three groups: run identification, bug/APPL_TOP identification, and prerequisite ordering.

• ANALYSIS_RUN_ID — identifies the specific Criteria Analysis execution that generated the dependency rows. This is the highest-level grouping key.
• APPL_TOP_ID — foreign key to AD_APPL_TOPS; identifies the application-tier installation against which the analysis was performed.
• BUG_NUMBER — the bug whose dependency is being recorded.
• PREREQ_BUG_NUMBER — the prerequisite bug that must be satisfied before BUG_NUMBER.
• PREREQ_BUG_ORDER — the ordinal position of the prerequisite within the dependency sequence, allowing deterministic ordering when multiple prerequisites exist.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard EBS audit columns recording who created or last modified each row and when.

The documented unique index AD_PA_ANAL_BUG_DEPS_U1 spans ANALYSIS_RUN_ID, BUG_NUMBER, APPL_TOP_ID, and PREREQ_BUG_NUMBER. This composite is the business-key candidate; there is no separately documented single-column surrogate primary key. The unique index guarantees that a given run cannot hold duplicate dependency entries for the same bug, APPL_TOP, and prerequisite bug.

Common Use Cases and Queries

Typical usage centers on prerequisite-chain reporting and post-analysis troubleshooting. A DBA may need to list every prerequisite recorded for a specific analysis run, or to identify all bugs depending on a particular prerequisite bug.

• Inventory of dependencies for the latest run:
  SELECT BUG_NUMBER, PREREQ_BUG_NUMBER, PREREQ_BUG_ORDER, APPL_TOP_ID FROM APPLSYS.AD_PA_ANAL_BUG_DEPS WHERE ANALYSIS_RUN_ID = :run_id ORDER BY BUG_NUMBER, PREREQ_BUG_ORDER;
• Reverse lookup — which bugs require a given prerequisite:
  SELECT BUG_NUMBER, ANALYSIS_RUN_ID FROM APPLSYS.AD_PA_ANAL_BUG_DEPS WHERE PREREQ_BUG_NUMBER = :bug;
• Join to AD_APPL_TOPS to resolve the application tier:
  SELECT d.BUG_NUMBER, d.PREREQ_BUG_NUMBER, t.NAME FROM APPLSYS.AD_PA_ANAL_BUG_DEPS d, APPLSYS.AD_APPL_TOPS t WHERE d.APPL_TOP_ID = t.APPL_TOP_ID AND d.ANALYSIS_RUN_ID = :run_id;
• Reconciliation of dependency counts per run for capacity or performance trending.

Because the table is populated by the Criteria Analysis process, it is generally queried read-only for diagnostics, and directly modified only under Oracle Support direction.

Related Objects

The documented foreign key from AD_PA_ANAL_BUG_DEPS.APPL_TOP_ID points to AD_APPL_TOPS.APPL_TOP_ID, making AD_APPL_TOPS the principal referenced table. Other AD objects that commonly participate in the same analysis and patching workflow include the analysis run headers (referenced by ANALYSIS_RUN_ID), the AD bug and patch inventory tables used to source BUG_NUMBER and PREREQ_BUG_NUMBER, and the AD utilities that consume the dependency set for ordering. The AD_APPL_TOPS join supplies the human-readable APPL_TOP name for reporting. Together these objects form the Criteria Analysis dependency model that AD utilities rely upon during patch prerequisite evaluation in both 12.1.1 and 12.2.2.