Results for “patch_type”

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

Overview

AD_APPLIED_PATCHES is a core Oracle Applications DBA (AD) repository table owned by the APPLSYS schema. It records the Oracle Applications patches that have been applied to, or imported into, an E-Business Suite environment. In both release 12.1.1 and 12.2.2 the table functions as the authoritative registry consulted by AutoPatch (adpatch) and by the Oracle Universal Installer-driven patching utilities to determine which patches, maintenance pack levels, and patch clusters are already present in the instance. Because it governs patch eligibility, prerequisite validation, and re-application prevention, the table is central to the lifecycle management of the EBS technology stack and the application tier.

From a heuristic Data Vault modeling perspective, the documented metadata classifies AD_APPLIED_PATCHES as standalone. This suggests the table behaves as a hub-like reference entity: it holds one durable business key (PATCH_NAME) and descriptive attributes, without participating in documented foreign-key relationships to other core hubs. The classification is a modeling suggestion, not a physical constraint, and the observed inbound reference from AD_SEED_DATA_LOADED indicates a lightweight dependency rather than a fully normalized link structure.

Key Information Stored

The table is documented with 15 columns in the 12.2.2 physical schema. The most operationally significant are:

• APPLIED_PATCH_ID — the surrogate primary key, enforced by AD_APPLIED_PATCHES_PK and also carried by the unique index AD_APPLIED_PATCHES_U1. It is the numeric identifier used for internal joins.
• PATCH_NAME — the business-key candidate, holding the patch number and name as distributed by Oracle (for example, a seven-digit patch identifier followed by a descriptive suffix). This is the value DBAs search on.
• PATCH_TYPE — distinguishes the class of patch, such as standalone, mini-pack, or maintenance pack, which drives prerequisite logic.
• MAINT_PACK_LEVEL — records the maintenance pack or family pack level associated with the applied patch.
• RAPID_INSTALLED_FLAG — indicates whether the patch was applied using the rapid install path rather than adpatch.
• SOURCE_CODE — identifies the origin or source classification of the patch record.
• IMPORTED_FLAG, IMPORTED_FROM_DB, and IMPORTED_ID — support records that were imported from another database rather than applied locally, a pattern common in cloned or consolidated environments.
• MERGE_DATE — the date on which the patch was merged into the instance.
• DATA_MODEL_DONE_FLAG — tracks whether the data-model portion of the patch has completed.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY — the standard EBS who-columns providing audit lineage.

Common Use Cases and Queries

The table is queried for patch-level reporting, pre-patch validation, and environment reconciliation. A typical query lists applied maintenance packs:

SELECT patch_name, patch_type, maint_pack_level, creation_date
FROM applsys.ad_applied_patches
WHERE patch_type = 'M'
ORDER BY creation_date DESC;

DBAs also use it to confirm whether a specific patch was already applied before running adpatch, and to compare two environments after a clone by joining on PATCH_NAME and filtering on IMPORTED_FLAG. Reconciliation reports frequently use MAX(CREATION_DATE) to identify the most recent patch activity.

Related Objects

AD_APPLIED_PATCHES is reference by AD_SEED_DATA_LOADED, which carries APPLIED_PATCH_ID as a foreign key pointing back to this table, linking seed-data load activity to the patch that introduced it. Patch history and patch-driver information are surfaced through the AD patch management views and adphx tables used by adpatch. The encompassing AD product schema also contains AD_PATCH_DRIVER, AD_PATCH_RUN, and related repositories that record patch execution detail, while FND_PRODUCT_INSTALLATIONS and AD_TRACKABLE_ENTITIES support installation-level reconciliation. Together these objects allow administrators to correlate a stored patch record with its execution history, its seed data, and the resulting product installation state.