Search Results applied_patch_id




Overview
Explore in AI Chat

Overview

The AD_APPLIED_PATCHES table is a core repository within the Oracle E-Business Suite (EBS) Applications DBA (AD) module. Owned by the APPLSYS schema, it serves as the definitive system of record for tracking all Oracle Applications patches applied to an EBS instance. Its primary role is to maintain a historical inventory of patch applications, which is critical for system maintenance, auditing, troubleshooting, and ensuring the integrity of the application's codebase. By querying this table, administrators can determine the precise patch level of their system, identify specific fixes that have been implemented, and avoid reapplying patches unnecessarily.

Key Information Stored

The table's structure is designed to capture essential metadata for each applied patch. While the full column list is proprietary, the documented primary key column, APPLIED_PATCH_ID, is a unique sequential identifier for each patch application record. Based on standard EBS architecture, the table typically stores information such as the patch number (e.g., a numeric RUP or mini-pack identifier or an alphanumeric bug fix number), the driver file name, the application top it was applied to, the date and time of application, the status of the application (e.g., applied, rolled back), and references to related AD worker jobs. This data provides a complete audit trail from the AD patch driver utility (adpatch).

Common Use Cases and Queries

The primary use case is generating reports on the patch history of an EBS environment. A fundamental query retrieves a list of recently applied patches, often sorted by application date. Administrators frequently query this table to verify if a specific patch or bug fix has been applied before implementing a change or troubleshooting an issue. It is also essential for compliance audits and during upgrade assessments to understand the current state of the system. A common reporting pattern involves joining with other AD tables to get more context on the patch run.

  • Sample Query: SELECT applied_patch_id, patch_name, applied_date FROM applsys.ad_applied_patches WHERE patch_name LIKE '%12345678%' ORDER BY applied_date DESC;
  • Use Case: Verifying the application of a specific bug fix (e.g., bug 12345678) before proceeding with a related functional test.

Related Objects

The AD_APPLIED_PATCHES table is central to the Applications DBA's data model. Its primary key, APPLIED_PATCH_ID, is referenced by foreign keys in other AD tables that store more granular details about a patch application. Key related objects include:

  • AD_PATCH_RUN_BUGS: Links applied patch runs to specific bug numbers.
  • AD_PATCH_RUNS: Contains high-level information about each execution of the adpatch utility, which may apply one or more patches.
  • AD_PATCH_DRIVER_LANGS: Stores details on language-specific driver files applied within a patch run.
  • AD_BUGS: The master table of bug definitions, which can be joined via intermediate tables to relate applied patches to known issues.

These relationships allow for comprehensive reporting that ties a patch application event to specific bugs, files, and execution sessions.