Patching Introduction
Purpose of ORACLE EBS Patching
1. To apply the latest product enhancements
2. To maintain oracle certified/supported product version
3. Security and critical updates
4. Bug Fixes
5. Upgrades
6. For interoperability and integration with other products such as Database, Fusion Middleware etc.
Patching Components (component wise tools)
Fusion MiddleWear Components like WebTier, Forms and Reports, Oracle_Common and WebLogic are patched using
opatch or bsu. (Particularly for WebLogic).
Patching Tools
Patch Contents
Downloading Patch
Patch needs to be downloaded from support.oracle.com and naming convention for a patch is p<patch no>.zip
What does adop/adpatch do
Copies files from patch directory to EBS File System
Executes database actions such as .sql
Generates files such as Generate Forms, Reports, JAR files etc.
Patch file structure
Patch Types, Codelines and Codelevels
Types of Patches
ADOP Basics
Understanding dual file system
• Introduced from R12.2 to reduce patching down time
• Application Tier File System Consists of fs1 and fs2 in base directory
• At a given time, one is designated as run and the other as patch
• “run” file system is used for running Oracle E-Business Suite i.e., users access “run” File System
• “patch” file system is used for Patching
• “adop” Utility is used to apply patches on the Patch File System
Introduction to ADOP
• Introduced from R12.2
• Stands for AD Online Patching
• Replaces “adpatch” in previous versions
• Can apply all Application Tier Patches except FMW or iAS patches
• Consists of 5 phases: Prepare, Apply, Finalize, Cutover and Cleanup
ADOP Phases
Important tables
Queries