Search Results ad_patch_common_actions




Overview
Explore in AI Chat

Overview

The AD_PATCH_COMMON_ACTIONS table is a core repository within the Oracle E-Business Suite Applications DBA (AD) module, specifically designed to support the Autopatch utility. It serves as a master catalog of standardized, reusable actions that can be executed during the application of patches, upgrades, or maintenance packs. By centralizing these actions, the table enables Autopatch to efficiently manage and track complex patching workflows, ensuring consistency and repeatability across different patching sessions in both EBS 12.1.1 and 12.2.2 environments. Its existence is fundamental to the automated patching infrastructure, acting as a reference point for the specific operations performed during software updates.

Key Information Stored

While the provided metadata does not list specific columns beyond key relationships, the table's primary purpose dictates the nature of its data. The central identifier is the COMMON_ACTION_ID, which is the table's primary key and uniquely defines each common action record. A critical foreign key column is LOADER_DATA_FILE_ID, which links to the AD_FILES table. This relationship suggests that a common action is often associated with a specific data or driver file (e.g., a database driver, copy driver, or SQL script) that is executed as part of the action. Other columns likely include descriptors for the action type, internal command logic, execution parameters, and status flags that Autopatch uses to process the action correctly.

Common Use Cases and Queries

The primary use case is for diagnostic and historical analysis of patching operations. Database administrators and functional consultants may query this table to understand the library of available actions or to investigate patching issues. For instance, to identify all common actions associated with a specific data file, one might execute a join on AD_FILES. A more frequent query involves joining with the AD_PATCH_RUN_BUG_ACTIONS table to see which common actions were executed for a particular patch run. A sample diagnostic query might be:

  • SELECT pca.common_action_id, pca.loader_data_file_id, af.file_name, prba.bug_id FROM apps.ad_patch_common_actions pca LEFT JOIN apps.ad_files af ON pca.loader_data_file_id = af.file_id LEFT JOIN apps.ad_patch_run_bug_actions prba ON pca.common_action_id = prba.common_action_id WHERE prba.patch_run_id = &run_id;

This helps trace the execution steps of a patch back to the predefined common actions.

Related Objects

The AD_PATCH_COMMON_ACTIONS table has defined relationships with two other key patching tables, forming a critical part of the AD patching schema.

  • Referenced Foreign Key (Outbound): The table references AD_FILES via the column AD_PATCH_COMMON_ACTIONS.LOADER_DATA_FILE_ID. This links a common action to its physical driver or data file.
  • Referencing Foreign Key (Inbound): The table is referenced by AD_PATCH_RUN_BUG_ACTIONS via the column AD_PATCH_RUN_BUG_ACTIONS.COMMON_ACTION_ID. This is the most significant relationship, as it logs every instance where a common action is executed for a specific bug fix within a patching session, creating the audit trail for patch runs.

These relationships position AD_PATCH_COMMON_ACTIONS as the central definitional table, with AD_FILES providing the executable component and AD_PATCH_RUN_BUG_ACTIONS recording the runtime execution history.