Results for “driver_type_d_flag”

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

Overview

AD_PATCH_DRIVERS is a core Applications DBA (AD) repository table in Oracle E-Business Suite, owned by the APPLSYS schema. It stores the metadata for the individual driver files that make up an applied patch. Each row corresponds to one driver — a worker file such as a unified (u) driver, a database (d) driver, or a generic (g) driver — that is executed or registered as part of the patch application lifecycle managed by the AutoPatch utility. In effect, the table records which drivers belong to which patch, their file identity, integrity attributes, and whether they are merged or imported.

The table resides in APPLSYS alongside the other AD patch-tracking objects and is populated during patch application and merging (for example, when a patch is merged into a consolidated or translated patch, or when a patch is imported from another environment). Under a Data Vault modeling interpretation, the documented FK structure classifies AD_PATCH_DRIVERS as hub-leaning: it carries a surrogate primary key and stable business keys, and is referenced by several surrounding tables. This classification is a heuristic suggestion drawn from the FK topology, not a prescribed design.

Key Information Stored

The primary key is AD_PATCH_DRIVERS_PK, defined on the surrogate column PATCH_DRIVER_ID. Two unique indexes act as business-key candidates: AD_PATCH_DRIVERS_U1 (PATCH_DRIVER_ID) and AD_PATCH_DRIVERS_U2 (FILE_CONTENTS_CHECKSUM, FILE_SIZE, DRIVER_FILE_NAME, APPLIED_PATCH_ID). The rows hold 22 documented columns; the most significant are:

• PATCH_DRIVER_ID — surrogate identifier and primary key for the driver record.
• APPLIED_PATCH_ID — foreign key to the patch to which the driver belongs.
• DRIVER_FILE_NAME — the physical name of the driver file.
• ORIG_PATCH_NAME — the original patch name that contributed the driver, useful when drivers are merged.
• DRIVER_TYPE_C_FLAG, DRIVER_TYPE_D_FLAG, DRIVER_TYPE_G_FLAG — flags identifying the driver category (copy, database, generic/unified).
• PLATFORM, PLATFORM_VERSION — target platform and version for the driver.
• FILE_SIZE, FILE_CONTENTS_CHECKSUM — integrity attributes used with the U2 unique key to detect duplicate or already-applied drivers.
• MERGED_DRIVER_FLAG, MERGE_DATE — indicate whether the driver was merged and when.
• IMPORTED_FLAG, IMPORTED_FROM_DB, IMPORTED_ID — track drivers brought in from another database or environment.
• SOURCE_CODE, PATCH_ABSTRACT — source classification and an abstract/description of the driver's content.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard EBS auditing columns.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include auditing which drivers an applied patch delivered, tracing merged drivers back to their originating patches, and detecting duplicates via the checksum and size columns.

• List drivers for a given patch, joined to the patch header:

  SELECT d.PATCH_DRIVER_ID, d.DRIVER_FILE_NAME, d.ORIG_PATCH_NAME,
         d.PLATFORM, d.FILE_SIZE
    FROM APPLSYS.AD_PATCH_DRIVERS d
   WHERE d.APPLIED_PATCH_ID = :applied_patch_id;

• Identify merged or imported drivers:

  SELECT PATCH_DRIVER_ID, DRIVER_FILE_NAME
    FROM APPLSYS.AD_PATCH_DRIVERS
   WHERE MERGED_DRIVER_FLAG = 'Y';

• Find duplicate drivers by business key:

  SELECT FILE_CONTENTS_CHECKSUM, FILE_SIZE, DRIVER_FILE_NAME,
         APPLIED_PATCH_ID, COUNT(*)
    FROM APPLSYS.AD_PATCH_DRIVERS
   GROUP BY FILE_CONTENTS_CHECKSUM, FILE_SIZE,
            DRIVER_FILE_NAME, APPLIED_PATCH_ID
  HAVING COUNT(*) > 1;

Related Objects

The table participates in a well-defined set of AD relationships:

• AD_COMPRISING_PATCHES — references AD_PATCH_DRIVERS.PATCH_DRIVER_ID, linking drivers to the composite patch that contains them.
• AD_PATCH_DRIVER_LANGS — references PATCH_DRIVER_ID, holding language-specific driver variants.
• AD_PATCH_DRIVER_MINIPKS — references PATCH_DRIVER_ID, storing mini-package information per driver.
• AD_PATCH_RUNS — references PATCH_DRIVER_ID, capturing individual driver execution runs during a patch.
• AD_PATCHES / patch header objects — the parent implied by APPLIED_PATCH_ID, joining AD_PATCH_DRIVERS to the applied patch record.

These relationships make AD_PATCH_DRIVERS a central hub for patch-driver tracking, supporting merge analysis, language expansion, minipak generation, and run-level auditing across the AD patch subsystem.