APPS DBA – Patching Driver Files

AutoPatch uses driver files to direct the installation of patch.  These driver files, or .drv files, are files that adpatch uses to determine what jobs to perform and these files are

ü  Copy driver

ü  Database  driver

ü  Generate Driver

ü  Unified Driver

Copy driver, cXXXXXX.drv

The copy driver is the first driver, which must be run using adpatch. This driver contains commands to change Oracle Applications files.

The commands include directives to copy and update files, libraries, and/or Java, and commands for generating JAR files and/or C executables.

In a multi-node system, the copy portion runs on all application tier APPL_TOPs.

Database driver, dXXXXXX.drv

Database driver, which is the second driver file executed. This driver contains 

commands to  change Oracle Applications database objects, such as PL/SQL 

and table definitions, or to update or migrate data. Some examples are scripts 

that

·         Create packages

·         Create new error message

·         Add a new table or view to the database

·         Add a new column to a table

·         Add new seed data to a table 

In a multi-node system, the database portion runs only on the application tier 

APPL_TOP that  implements the administration server

Generate Driver, gXXXXXX.drv

Generate Driver Contains commands to generate forms, reports, messages, and/or graphics files.

In a multi-node system, the generate portion runs on all application tier APPL_TOPs, unless the APPL_TOP only implements the administration server. The following are some examples of commands in a ‘g’ driver.

·         The .fmb files are stored in $AU_TOP, and when generated the executable (.fmx) is stored under the product.

·         The .pll is stored under $AU_TOP, and when generated the executable (.plx) is also stored under $AU_TOP.

Unified Driver, uXXXXXX.drv

This unified driver is named u<patchnumber>.drv. It contains all the driver actions (copy, database, and generate) that the patch requires, and it performs these actions in the stated order.

Typically, you run the driver on all APPL_TOPs and AutoPatch determine which actions are required for the current APPL_TOP and run only those actions. 

Reference Tables:

AD_PATCH_DRIVERS: This table holds information about all patch drivers included in specific patch

AD_PATCH_DRIVER_LANGS: NLS patches (or more specifically, NLS patch drivers) pertain to a language or multiple languages

AD_PATCH_DRIVER_MINIPKS: This table holds information about the various Mini Packs contained in a patch (driver)

Links: http://appsvista.blogspot.com/2011/01/apps-dba-patching-basic-info.html