Search Results ad_patch_drivers




Overview
Explore in AI Chat

Overview

The AD_PATCH_DRIVERS table is a core repository table within the Oracle E-Business Suite Applications DBA (AD) module. It functions as the master registry for all individual patch driver files that constitute an applied patch. In the context of Oracle EBS patching, a patch (or mini-pack) is typically comprised of multiple driver files (e.g., c.drv, d.drv, g.drv), each responsible for a specific type of change such as copying database objects, updating database code, or merging Java archives. This table, owned by the APPLSYS schema, provides the critical link between a high-level patch and its constituent executable components, enabling the patching system (AD_ZD_PATCH) to track, manage, and report on the application of these drivers across both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the structure and foreign key relationships define its key data elements. The primary key, PATCH_DRIVER_ID, uniquely identifies each driver record. A critical foreign key column, APPLIED_PATCH_ID, links the driver back to its parent patch record in the AD_PATCH_DRIVERS table itself (a self-referencing relationship) or more logically to a master patch record. Other columns typically store the driver file name, driver type (C, D, G, etc.), the source language, application top directory, and status information. This structure allows the system to maintain a precise inventory of every file action performed during a patching cycle.

Common Use Cases and Queries

This table is primarily accessed for diagnostic and auditing purposes by Applications DBAs. Common use cases include investigating failed patch sessions, generating patch application reports, and understanding the composition of applied patches. A fundamental query retrieves all drivers for a specific applied patch, often joined with the AD_PATCH_RUNS table to see execution details.

  • Identifying Drivers in a Patch: SELECT patch_driver_id, driver_file_name, driver_type FROM applsys.ad_patch_drivers WHERE applied_patch_id = (SELECT patch_driver_id FROM applsys.ad_patch_drivers WHERE driver_file_name LIKE '%<PATCH_NUMBER>%');
  • Patch Application History: Joining with AD_PATCH_RUNS to correlate drivers with their run status and timing: SELECT drv.driver_file_name, run.patch_driver_id, run.start_date, run.end_date, run.status FROM applsys.ad_patch_drivers drv, applsys.ad_patch_runs run WHERE drv.patch_driver_id = run.patch_driver_id ORDER BY run.start_date DESC;

Related Objects

The AD_PATCH_DRIVERS table sits at the center of a network of patching metadata tables, as indicated by its foreign key constraints. Key related objects include:

  • AD_COMPRISING_PATCHES: Links patch drivers to the comprehensive patches they belong to, managing complex patch dependencies and bundles.
  • AD_PATCH_DRIVER_LANGS: Stores language-specific information for each driver, detailing which translations were applied.
  • AD_PATCH_DRIVER_MINIPKS: Associates drivers with specific mini-packs, a common patching unit in EBS.
  • AD_PATCH_RUNS: The most operationally significant related table. It records every execution attempt of a patch driver, including start/end times, phase, and success/failure status, providing the execution audit trail.