Results for “patch_abstract”

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

Overview

AD_COMPRISING_PATCHES is an Applications DBA (AD) repository table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the constituent patches contained within a merged patch. When Oracle releases an aggregated patch — a merged rollup such as a consolidated update or a combined family pack — the individual patches it supersedes are tracked as "comprising patches." This table serves as the authoritative mapping between a merged patch and each of the bug fixes and patch drivers it delivers, allowing administrators and the patching utilities (ADOP/AD Patch) to determine exactly which fixes are present once a merged patch is applied.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a link. It functions as an associative table resolving the many-to-many relationship between merged patches and the bugs (patches) they comprise, rather than as a descriptive hub or satellite. This classification is a modeling suggestion drawn from the foreign-key structure and is not an Oracle-imposed designation.

Key Information Stored

• COMPRISING_PATCH_ID — The surrogate primary key, uniquely identifying each comprising-patch record. It is enforced by AD_COMPRISING_PATCHES_PK and the unique index AD_COMPRISING_PATCHES_U1.
• PATCH_DRIVER_ID — Foreign key to AD_PATCH_DRIVERS, linking the record to the patch driver (the executable patch definition) that the merged patch embodies.
• BUG_ID — Foreign key to AD_BUGS, identifying the underlying bug or individual patch represented within the merged patch.
• PATCH_ABSTRACT — A textual description summarizing the nature of the comprising patch, useful for reporting without joining to the bugs table.
• CREATED_BY / CREATION_DATE — Standard audit columns capturing who inserted the row and when.
• LAST_UPDATED_BY / LAST_UPDATE_DATE — Standard audit columns capturing the most recent modification and its author.

The composite unique index AD_COMPRISING_PATCHES_U2 (PATCH_DRIVER_ID, BUG_ID) is the business-key candidate, guaranteeing that any given bug is listed only once per patch driver, preventing duplicate comprising entries.

Common Use Cases and Queries

Administrators and DBAs query this table to answer which individual fixes are bundled inside a merged patch, to verify that a required bug fix was absorbed into a rollup, and to audit patch history. A representative query retrieves all comprising bugs for a given patch driver:

• SELECT c.bug_id, c.patch_abstract FROM ad_comprising_patches c WHERE c.patch_driver_id = :driver_id;
• SELECT p.patch_name, c.bug_id FROM ad_comprising_patches c JOIN ad_patch_drivers p ON c.patch_driver_id = p.patch_driver_id WHERE c.bug_id = :bug_id;
• Reporting tools use PATCH_ABSTRACT for human-readable patch summaries in patch impact and remediation reports.

Related Objects

• AD_PATCH_DRIVERS — Join on AD_COMPRISING_PATCHES.PATCH_DRIVER_ID = AD_PATCH_DRIVERS.PATCH_DRIVER_ID; supplies the merged patch definition.
• AD_BUGS — Join on AD_COMPRISING_PATCHES.BUG_ID = AD_BUGS.BUG_ID; supplies the underlying bug details.
• AD_PATCH_DRIVER_LANGUAGES, AD_PATCH_RUN_BUGS, and AD_PATCH_RUNS — related AD patching tables commonly queried alongside for full patch lifecycle reporting.
• AD_APPLIED_PATCHES — records applied patches and is frequently correlated with comprising-patch data during patch verification.