Search Results ad_patch_driver_minipks
Overview
The AD_PATCH_DRIVER_MINIPKS table is a core repository table within the Applications DBA (AD) product family of Oracle E-Business Suite (EBS), versions 12.1.1 and 12.2.2. Residing in the APPLSYS schema, it serves a critical function in the patch application architecture. Its primary role is to track and manage the specific Mini Packs that are bundled within a larger patch driver file. A Mini Pack is a discrete, logical grouping of files and code changes. This table enables the Oracle Applications Manager (OAM) and the underlying AD utilities to accurately inventory, validate, and apply the individual components that constitute a delivered patch, ensuring a structured and auditable patching process.
Key Information Stored
The table's structure is designed to map Mini Packs to their parent patch drivers. The most significant column, as indicated by the user's search for "minipk_id," is the MINIPK_ID itself. This column serves as the table's primary key, uniquely identifying each Mini Pack record within the system. Another essential column is PATCH_DRIVER_ID, which acts as a foreign key linking back to the parent patch driver record in the AD_PATCH_DRIVERS table. This relationship defines which driver contains which Mini Packs. While the provided metadata does not list additional columns, typical related data would include version information, sequence or order of application, and status flags for the Mini Pack within the context of its driver.
Common Use Cases and Queries
This table is primarily queried for diagnostic and reporting purposes related to the EBS patching lifecycle. Common scenarios include verifying the contents of an applied patch, troubleshooting failed patch sessions, and generating inventory reports. A fundamental query involves joining with AD_PATCH_DRIVERS to list all Mini Packs for a specific driver. For example, to find details of Mini Packs within a known driver, one might use: SELECT minipk_id FROM applsys.ad_patch_driver_minipks WHERE patch_driver_id = &driver_id;. System administrators may also run queries to audit patch history or to understand dependencies between applied Mini Packs when diagnosing system issues.
Related Objects
The AD_PATCH_DRIVER_MINIPKS table has a direct and documented foreign key relationship with the AD_PATCH_DRIVERS table, which is central to the AD patching framework. The relationship is defined as follows:
- Foreign Key From: AD_PATCH_DRIVER_MINIPKS
- Foreign Key To (Parent Table): AD_PATCH_DRIVERS
- Join Column: AD_PATCH_DRIVER_MINIPKS.PATCH_DRIVER_ID references AD_PATCH_DRIVERS
-
Table: AD_PATCH_DRIVER_MINIPKS
12.2.2
owner:APPLSYS, object_type:TABLE, fnd_design_data:AD.AD_PATCH_DRIVER_MINIPKS, object_name:AD_PATCH_DRIVER_MINIPKS, status:VALID, product: AD - Applications DBA , description: Mini Packs contained in a patch (driver) , implementation_dba_data: APPLSYS.AD_PATCH_DRIVER_MINIPKS ,
-
Table: AD_PATCH_DRIVERS
12.2.2
owner:APPLSYS, object_type:TABLE, fnd_design_data:AD.AD_PATCH_DRIVERS, object_name:AD_PATCH_DRIVERS, status:VALID, product: AD - Applications DBA , description: Patch drivers in a patch , implementation_dba_data: APPLSYS.AD_PATCH_DRIVERS ,