Results for “onsite_file_version_id”

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

Overview

APPLSYS.AD_PATCH_RUN_BUG_ACTIONS is an Oracle E-Business Suite Applications DBA (AD) transactional table that records the individual actions contained within a bug (fix) processed during a specific patch run. Each row represents one atomic operation — a file copy, a SQL script execution, a Java class load, or similar step — associated with a bug fix delivered through Oracle's patching infrastructure. The table is central to the AD patching data model, forming the operational link between a patch run's bug inventory and the physical files, file versions, and common action definitions that the patching engine must apply.

Because the table carries foreign keys to multiple independent entities — bugs, files, file versions, and common action types — its heuristic Data Vault classification as a link table is consistent with its structure. In a Data Vault model, this would typically be modeled as a link connecting the patch-run-bug hub to file, file-version, and common-action hubs, with execution status and audit attributes carried as link-level descriptive payload. Analysts should treat this as a modeling suggestion only; the physical table remains a normalized relational structure owned by APPLSYS with fourteen documented columns in ETRM 12.2.2.

Key Information Stored

The surrogate primary key is ACTION_ID, enforced by AD_PATCH_RUN_BUG_ACTIONS_PK and also backed by the unique index AD_PATCH_RUN_BUG_ACTIONS_U1. A second unique index, AD_PATCH_RUN_BUG_ACTIONS_U2 on (PATCH_RUN_BUG_ID, FILE_ID, COMMON_ACTION_ID), identifies the principal business-key candidate: it guarantees that a given file receives a given common action at most once within a single patch-run bug.

The most operationally significant columns are:

• PATCH_RUN_BUG_ID — foreign key to AD_PATCH_RUN_BUGS; identifies the parent bug occurrence within a patch run.
• COMMON_ACTION_ID — foreign key to AD_PATCH_COMMON_ACTIONS; defines the action type (for example, copy, generate, or run).
• FILE_ID — foreign key to AD_FILES; the file the action targets.
• PATCH_FILE_VERSION_ID — foreign key to AD_FILE_VERSIONS; the patched version of the file to be applied.
• ONSITE_FILE_VERSION_ID — foreign key to AD_FILE_VERSIONS; the version currently present in the customer's environment prior to the action.
• ONSITE_PKG_VERSION_IN_DB_ID — foreign key to AD_FILE_VERSIONS; the database-side packaged version resident on site, supporting version reconciliation.
• DEST_FILE_ID and FILE_TYPE_FLAG — identify the destination file and the classification of the file being processed.
• EXECUTED_FLAG — indicates whether the action has been executed, driving idempotency and restart behavior for the patching engine.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns capturing who created and last modified each action record.

Common Use Cases and Queries

The primary use case is failure diagnosis and restart of a failed or partial patch run. DBAs join this table to AD_PATCH_RUN_BUGS and AD_PATCH_RUNS to determine which actions were left unexecuted. A representative pattern:

• Identifying pending actions for a run: SELECT A.ACTION_ID, A.PATCH_RUN_BUG_ID, A.FILE_ID, A.COMMON_ACTION_ID FROM AD_PATCH_RUN_BUG_ACTIONS A, AD_PATCH_RUN_BUGS B WHERE A.PATCH_RUN_BUG_ID = B.PATCH_RUN_BUG_ID AND A.EXECUTED_FLAG = 'N';
• Resolving the semantic action name by joining COMMON_ACTION_ID to AD_PATCH_COMMON_ACTIONS.
• Version reconciliation for a target file, joining PATCH_FILE_VERSION_ID, ONSITE_FILE_VERSION_ID, and ONSITE_PKG_VERSION_IN_DB_ID to AD_FILE_VERSIONS.
• File-level impact reporting, aggregating executed and unexecuted actions by FILE_ID and FILE_TYPE_FLAG.

Typical reporting outputs include per-run action counts, success/failure ratios by action type, and audit trails of when each action was applied.

Related Objects

• AD_PATCH_RUN_BUGS — parent of the action rows via PATCH_RUN_BUG_ID.
• AD_PATCH_COMMON_ACTIONS — action-type lookup referenced by COMMON_ACTION_ID.
• AD_FILES — target file registry referenced by FILE_ID.
• AD_FILE_VERSIONS — version registry referenced three times via PATCH_FILE_VERSION_ID, ONSITE_FILE_VERSION_ID, and ONSITE_PKG_VERSION_IN_DB_ID.
• AD_PATCH_RUNS — the enclosing patch run that links each bug to an execution session.