How to apply weblocig Patches in R12.2
Before jumping into actual patching, it helps to understand the technology stack behind Oracle E-Business Suite (EBS) 12.2 patching.
This includes the tools used for each component.
This post gives a quick background on Application Technology patches, with a focus on the WebLogic Server (BSU) patching process.
What Are Application Technology Patches?
Application Technology patches cover the middle-tier components of EBS 12.2 and are applied using different utilities depending on the component:
| Component | Home | Patching Tool |
|---|---|---|
| Oracle HTTP Server (OHS) | OHS Home | OPatch |
| Oracle WebLogic Server | FMW Home | BSU (Smart Update) |
| Oracle Forms (10.1.2 ORACLE_HOME) | Forms Home | OPatch |
These patches can be applied directly on the Run edition, after which adop fs_clone is executed to sync the file system. Alternatively, they can be applied through the standard Patch edition cycle as part of an adop patching session.
Applying Middle Tier ETCC Patches
As part of routine maintenance, two key patch categories should be kept current:
- Download and apply the latest ETCC Patch from My Oracle Support, Doc ID 17537119.
- Download and apply the latest WebLogic patches, referencing My Oracle Support Doc ID 1594274.1.
WebLogic (BSU) Patching
BSU (Smart Update) is a Java-based utility used specifically to apply patches to the Oracle WebLogic Server component of the EBS middle tier.
Location:
$FMW_HOME/utils/bsu/bsu.shWebLogic patch IDs typically follow a short alphanumeric format, for example: VA89.
Important Directories / Paths
These are the key directories and paths referenced throughout the BSU patching process:
BSU utility location:$FMW_HOME/utils/bsu/bsu.sh
BSU patch cache directory (where patch JAR files are placed):$FMW_HOME/utils/bsu/cache_dir
Environment file to source (Patch edition mode):/apps/VIS/r12/fs2/EBSapps.env patch
WebLogic server product directory (target for patch install):$FMW_HOME/wlserver_10.3
Step-by-Step Patch Application
Step 1 — Download the Patch
Download the required patch from Oracle Support (My Oracle Support / Metalink).
Step 2 — Unzip the Patch
Extract the downloaded zip file. It will contain a JAR file and a README file.
Step 3 — Place the Patch in the Cache Directory
Copy the patch JAR file (for example, Q3ZB.jar) into the BSU cache directory. The README file is not required here.
[oracle@VIS cache_dir]$ pwd
$FMW_HOME/utils/bsu/cache_dirStep 4 — Source the Patch File System
Source the environment file in patch mode and confirm the file edition.
[oracle@VIS ~]$ . /apps/VIS/r12/fs2/EBSapps.env patch
[oracle@VIS ~]$ echo $FILE_EDITION
PatchStep 5 — Apply the Patch Using BSU
export CONFIG_JVM_ARGS="-Xms512m -Xmx1024m"
export T2P_JAVA_OPTIONS="-Djava.io.tmpdir=/tmp -Xms512m -Xmx1024m"
[oracle@VIS bsu]$ ./bsu.sh -install \
-patch_download_dir=$FMW_HOME/utils/bsu/cache_dir \
-patchlist=Q3ZB \
-prod_dir=$FMW_HOME/wlserver_10.3
Checking for conflicts..
No conflict(s) detected
Installing Patch ID: Q3ZB..
Result: SuccessCommon WebLogic Patch Commands
Check installed patches
./bsu.sh -prod_dir=$FMW_HOME/wlserver_10.3 -status=applied -verbose -view
./bsu.sh -report | grep "Q3ZB"Apply a patch
./bsu.sh -install \
-patch_download_dir=/apps/applmgr/r12/fs1/FMW_Home/utils/bsu/cache_dir \
-patchlist=Q3ZB \
-prod_dir=$FMW_HOME/wlserver_10.3Remove a patch
./bsu.sh -prod_dir=$FMW_HOME/wlserver_10.3 -remove -patchlist=159X,M3C7,WFNK,LLU8,U5I2Find the WebLogic patch version
java -cp $FMW_HOME/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:$FMW_HOME/wlserver_10.3/server/lib/weblogic.jar weblogic.version | grep PSU | awk '{print $1 " " $2 " " $3}'BSU Command Parameters Reference
| Parameter | Description |
|---|---|
-help | Displays a summary of BSU parameters and arguments |
-patch_download_dir=path | Specifies the patch download directory. If omitted, BSU uses the directory set in the Smart Update GUI preferences |
-verbose | Displays the full set of details associated with each applied patch |
-prod_dir=path | Specifies the target installation to which patches are applied |
-gui | Starts Smart Update in graphical interface mode |
-log | Creates a log file at a specified location (-log_priority={trace|debug|info|warn|error|fatal}) |
-remove | Removes patches from the profile |
-report | Generates a report showing applied patches and detailed file changes |
-version | Displays version information, e.g., "Oracle Smart Update. Version: 3.3.3.0" |
Troubleshooting Patching Failures
If a BSU patch fails to apply, or conflicts are detected, the following My Oracle Support references are useful starting points:
- WebLogic Server PSU – Popular Known Issues (Doc ID 2458832.1)
- WLS BSU (Smart Update) Takes a Very Long Time to Apply Patches — especially during conflict checking (Doc ID 2271366.1)
- Diagnosing "Encountered unrecognized patch ID" Failures when patching WLS using BSU (Doc ID 1186923.1)
- Conflict Detected — mutually exclusive PSU errors for WLS 10.3.6 (Doc ID 2267696.1)
- Native Windows Zip/Unzip Tools Fail to Extract Patch Zip Files — "Path Too Long" or "is Invalid" errors (Doc ID 2259579.1)
References
- Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1)
- How to Apply WebLogic Server (WLS) Patches Using Smart Update (Doc ID 876004.1)
- BSU Command Line Interface — Oracle Documentation
This comment has been removed by the author.
ReplyDelete