Results for “patch_level”

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

Overview

AD_PATCH_DRIVER_MINIPKS is an Oracle E-Business Suite reference table owned by the APPLSYS schema and belonging to the AD (Applications DBA) product. It records the individual mini-packs (minipacks) that are included within an Oracle Applications patch as declared by that patch's driver file. Each row associates a patch driver with a specific application short name and patch level, allowing the AutoPatch (adpatch) utility and related AD utilities to determine which mini-packs a given patch delivers.

The object is documented as VALID in both EBS 12.1.1 and 12.2.2. In the ETRM metadata it is described simply as "Mini Packs contained in a patch (driver)," which confirms its role as a child or detail table within the patch-driver subsystem. The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning, suggesting that AD_PATCH_DRIVER_MINIPKS behaves primarily as a descriptive satellite attached to its parent driver record in AD_PATCH_DRIVERS. It carries attributes (application, patch level, audit columns) rather than acting as an independent hub or a pure many-to-many link.

Key Information Stored

The table is physically defined with eight columns in APPLSYS. The most significant are:

• MINIPK_ID — the surrogate primary key. It is enforced by both the AD_PATCH_DRIVER_MINIPKS_PK constraint and the unique index AD_PATCH_DRIVER_MINIPKS_U1, making it the definitive row identifier.
• PATCH_DRIVER_ID — foreign key to AD_PATCH_DRIVERS. This links each mini-pack entry back to its owning patch driver.
• APP_SHORT_NAME — the application short name (for example, GL, AP, or INV) to which the mini-pack belongs.
• PATCH_LEVEL — the patch level or version identifier delivered by the mini-pack.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — the standard EBS audit columns that record who created the row and when, and who last modified it.

The combination of PATCH_DRIVER_ID and APP_SHORT_NAME is a documented business-key candidate, enforced by the unique index AD_PATCH_DRIVER_MINIPKS_U2. This ensures that a given application appears at most once per patch driver, while MINIPK_ID remains the surrogate key used for referential integrity.

Common Use Cases and Queries

Typical uses include auditing which applications and patch levels a patch delivers, reconciling applied patches against their drivers, and building patch inventory reports. For example, listing all mini-packs for a specific driver:

• SELECT m.MINIPK_ID, m.APP_SHORT_NAME, m.PATCH_LEVEL FROM APPLSYS.AD_PATCH_DRIVER_MINIPKS m WHERE m.PATCH_DRIVER_ID = :driver_id ORDER BY m.APP_SHORT_NAME;
• SELECT d.PATCH_NAME, m.APP_SHORT_NAME, m.PATCH_LEVEL FROM APPLSYS.AD_PATCH_DRIVERS d, APPLSYS.AD_PATCH_DRIVER_MINIPKS m WHERE d.PATCH_DRIVER_ID = m.PATCH_DRIVER_ID AND m.APP_SHORT_NAME = 'GL';

These queries support DBA troubleshooting when investigating patch application failures, verifying that a particular application's mini-pack is present in a driver, and producing compliance or upgrade-readiness reports.

Related Objects

The most significant related object is the parent driver table:

• AD_PATCH_DRIVERS — joined via AD_PATCH_DRIVER_MINIPKS.PATCH_DRIVER_ID = AD_PATCH_DRIVERS.PATCH_DRIVER_ID. This is the sole documented foreign-key relationship and the principal parent in the patch-driver hierarchy.
• AD_PATCH_DRIVER_MINIPKS_PK / U1 / U2 — the primary-key constraint and unique indexes that enforce row identity and the business key.
• AD_APPLIED_PATCHES / AD_PATCH_RUN_* — tables in the AD patching subsystem that record applied patches and execution history, which DBAs commonly correlate with driver and mini-pack data during reconciliation.

Together these objects form the patch-driver subsystem that AD utilities consult to understand and execute the content of Oracle Applications patches.