Search Results ad_comprising_patches




Overview
Explore in AI Chat

Overview

The AD_COMPRISING_PATCHES table is a core metadata repository within the Oracle E-Business Suite (EBS) Applications DBA (AD) module. It functions as a critical component of the Oracle Applications Patch Technology stack, specifically designed to manage the composition of merged patches. In EBS 12.1.1 and 12.2.2, a merged patch is a single, consolidated patch file that contains multiple individual patches or bug fixes. This table provides the system of record that tracks which specific patches (or bugs) are included within a given merged patch driver, enabling accurate dependency tracking, patch history, and impact analysis during application maintenance cycles.

Key Information Stored

The table's structure centers on linking a parent patch driver to its constituent elements. The primary and foreign key relationships define its core data model. The key columns include:

  • COMPRISING_PATCH_ID: The primary key identifier for each record in this table.
  • PATCH_DRIVER_ID: A foreign key referencing the AD_PATCH_DRIVERS table. This identifies the parent merged patch that contains the component.
  • BUG_ID: A foreign key referencing the AD_BUGS table. This identifies the specific bug fix or patch that is a component of the merged patch. This is the fundamental link that enumerates what is inside a merged patch.

Common Use Cases and Queries

This table is essential for administrative reporting and troubleshooting. A primary use case is to generate a bill of materials for a recently applied merged patch, which helps DBAs understand its scope and potential impact. For instance, to list all individual bug fixes contained within a specific merged patch, one would join AD_COMPRISING_PATCHES to AD_PATCH_DRIVERS and AD_BUGS. Conversely, to identify which merged patch delivered a particular bug fix, the query would start from a known BUG_ID. This is crucial for validating patch applications, diagnosing issues post-patching, and auditing the patch history of an EBS instance. Sample queries often filter on the driver file name from AD_PATCH_DRIVERS or a specific bug number.

Related Objects

The AD_COMPRISING_PATCHES table has direct, integral relationships with other key AD tables, as defined by its foreign keys. The primary parent table is AD_PATCH_DRIVERS, which stores metadata about the patch driver itself (e.g., driver file name, type, application tier). The link to AD_BUGS provides detailed information about each comprising fix, such as the bug number, description, and associated product. This table is part of a larger schema for patch management that includes objects like AD_PATCHES, AD_PATCH_RUNS, and AD_APPLIED_PATCHES, which track the execution and application history of patches within the EBS environment.