ADPATCH

ADPATCH GENERAL INFORMATION

1.What is a patch driver file?
2.What are the Oracle Applications patch types?
3.Patches can also be organized by purpose.


1.What is a patch driver file?
AutoPatch uses a driver file to direct the installation of a patch. This unified driver is named u.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 determines which actions are required for the current APPL_TOP and runs only those actions.

The driver actions are as follows:

1.1 Copy

1.2 Database

1.3 Generate

Copy: 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: Contains commands to change Oracle Applications database objects, such as PL/SQL and table definitions, or to update or migrate data. In a multi-node system, the database portion runs only on the application tier APPL_TOP that implements the administration server.

Generate: 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.

2.What are the Oracle Applications patch types?

2.1 Standalone (one-off) Patch:

2.2 Rollup Patch (RUP)

2.3 Minipack

2.4 Family Pack

2.5 Maintenance Pack

All Applications patches are organized by aggregation level.

Standalone (one-off) Patch: Addresses a single fix or enhancement. Standalone patches are released only when there is an immediate need for a fix or enhancement that cannot wait until an aggregate bundling is available. Although standalone patches are intended to be as small as possible, they usually include any dependent files that have changed since the base release in order to form a complete patch that can be applied by any customer. The actual number of files changed will depend on the current code level on the system to which the patch is being applied.

Rollup Patch (RUP): An aggregation of patches that may be at the functional level, or at a specific product/family release level. For example, a Flexfields rollup patch contains all the latest patches related to Flexfields at the time the patch was created. A Marketing Family 11.5.10 rollup patch contains all the latest Marketing patches released since, and applicable to, 11.5.10.

Minipack: An aggregation of patches at the product level. For example, Inventory Minipack G (11i.INV.G) contains all the latest patches for the Inventory product at the time the minipack was created. Minipacks are named in alphabetical sequence such as 11i.INV.E, 11i.INV.F, 11i.INV.G, and so on. Minipacks are cumulative. In other words, 11i.INV.G contains everything in 11i.INV.F, which contains everything in 11i.INV.E, and so on. The terms patchset and minipack are often used interchangeably.

Family Pack: An aggregation of patches at the product family level. For example, Financials Family Pack C (11i.FIN_PF.C) contains all the latest patches for products in the Financials family at the time the family pack was created. Family product codes always end in "_PF" and family packs are given alphabetical sequence such as 11i.HR_PF.B, 11i.HR_PF.C, and 11i.HR_PF.D. Family packs are cumulative. In other words, Discrete Manufacturing Family Pack G (11i.DMF_PF.G) contains everything in 11i.DMF_PF.F, which contains everything in 11i.DMF_PF.E, and so on.

Maintenance Pack: An aggregation of patches for all products in the E-Business Suite. For example, Release 11.5.10 Maintenance Pack contains all the latest code level for all products at the time 11.5.10 was created. Maintenance packs are numbered sequentially such as 11.5.8, 11.5.9, 11.5.10, and are cumulative. In other words, 11.5.10 contains everything in 11.5.9, which contains everything in 11.5.8, and so on.

In addition to the patches in a maintenance pack, Oracle also packages a new Rapid Install at each maintenance pack release level. So Applications Release 11.5.10CU2 Rapid Install contains the same applications code level that a customer would get if they applied the Release 11.5.10CU1 Maintenance Pack on an earlier 11i release level. Note that the technology stack could still be different because Rapid Install includes the latest certified technology stack. The maintenance pack includes only Applications code.

Maintenance packs can be downloaded from OracleMetaLink or ordered as a CD Pack from the Oracle Store.

3. Patches can also be organized by purpose.

3.1 Diagnostic Patch

3.2 Interoperability Patch

3.3 Translated Patch

3.4 Merged Translation Patch

3.5 Translation Fix

3.6 New Feature Patch

3.7 Consolidated Update (CU)

3.8 Family Consolidated Upgrade Patch

3.9 Documentation Patch

Diagnostic Patch: Used to gather additional information when a product failure cannot be reproduced by Oracle. The additional information assists Oracle Support Services and Oracle Development in resolving the failure.

Interoperability Patch: Allows Oracle Applications to function properly with a newer version of the technology stack. Interoperability patches are typically required with new versions of the database or Applications technology stack.

Translated Patch: A non-English version of a patch. Release 11i supports 30 non-English languages. Customers who are using languages other than English, need to apply the corresponding translated patch(es) for the languages they are using in addition to any base US patch(es).

Merged Translation Patch: Provided in real time (without requiring a translator) in the event a translated patch is not available when a customer needs it. A merged translation patch is applied just like a fully translated patch. The fully translated patch is escalated and is usually available within 24 hours. It can be applied safely on top of a merged translation patch.

Translation Fix: Provided in the event a translation word choice is inappropriate. A translation fix is applied just like a translated patch, except there is no corresponding base US patch.

New Feature Patch: Introduces new functionality and/or products. It is applied using standard patching utilities.

Consolidated Update (CU): Improves and streamlines the upgrade and maintenance processes by consolidating certain post-release patches. Most recommended patches and rollups for a particular maintenance release are consolidated into a single patch that is installed immediately following application of a maintenance pack or a new installation of Rapid Install. Updates in the CU are predominantly error corrections.

Family Consolidated Upgrade Patch: Consolidates all upgrade-related patches from all the products within a product family. Family consolidated upgrade patches are released as needed and are applicable only if you are upgrading to Release 11i from Release 10.7 or 11.0. The Oracle Applications Release Notes, Release 11i (11.5.10.2), Note 316803.1 lists the most recent patches.

Documentation Patch: Updates online help.