Applying WebLogic Patch Set Update

Description: Demonstrates how to apply a WebLogic Patch Set Update (PSU) in general. As an example, critical patch 29633432 (MXLE - WLS 10.3.6.0.190716) is applied to WebLogic 10.3.6 on a Linux machine.

References:
https://www.oracle.com/technetwork/topics/security/alerts-086861.html
WebLogic Server PSU - Popular Known Issues (Doc ID 2458832.1)
Critical Patch Update (CPU) Program July 2019 Patch Availability Document (PAD) (Doc ID 2534806.1)
Patch 29633432: SU Patch MXLE:WLS PATCH SET UPDATE 10.3.6.0.190716

Apply WebLogic Patch

1. Download the critical WebLogic patch from Oracle Support.
   Patch Number : 29633432
   Patch ID: MXLE
   Patch Description: WLS PATCH SET UPDATE 10.3.6.0.190716
   File Name: p29633432_1036_Generic.zip
   
   
2. Shutdown all WebLogic server instances and the node managers.
   
   
3. Unzip the patch to the WebLogic cache directory. Then remove the README.txt file.
   export MW_HOME=/home/oracle/Oracle/Middleware
   unzip p29633432_1036_Generic.zip -d $MW_HOME/utils/bsu/cache_dir
   rm $MW_HOME//utils/bsu/cache_dir/README.txt
   
   
4. Run the BEA Smart Update (bsu.sh) script via command line to apply the WebLogic patch.
   cd $MW_HOME/utils/bsu/cache_dir
   export WL_HOME=/home/oracle/Oracle/Middleware/wlserver_10.3# Apply WebLogic Patch via BSU
   ./bsu.sh -install -patch_download_dir={MW_HOME}/utils/bsu/cache_dir -patchlist={PATCH_ID} -prod_dir=\was{WL_HOME} -verbose -log={LOG_FILE}
   
   # Example
   ./bsu.sh -install -patch_download_dir=$MW_HOME/utils/bsu/cache_dir -patchlist=MXLE -prod_dir=$WL_HOME -verbose -log=/home/oracle/bits/WebLogicPatch_Apply_MXLE_29633432.log
   
   
   
5. Verify WebLogic patch is applied via BSU or WebLogic console.
   # BSU Command Line
   ./bsu.sh -view -status=applied -prod_dir=$WL_HOME
   
   
   # WebLogic Console:  Servers -> AdminServer -> Monitoring -> WebLogic Version 
   
   

Troubleshooting

• Issue#1: java.lang.OutOfMemoryError: GC overhead limit exceeded
  
  Resolution: Modify the bsu.sh script to increase memory.
  
  
  
• Issue#2: Patch conflicts e.g. old patch is a subset of the new patch or one-off patch is specific to WebLogic critical patch version
  
  Resolution: Remove the patches in conflict.
  # Removing WebLogic Patch via BSU
  ./bsu.sh -remove -patchlist={Patch ID or comma separated Patch IDs} -prod_dir={WL_HOME} -verbose -log={LOG_FILE_PATH} 
  
  # Example
  ./bsu.sh -remove -patchlist=FSG4,XA6W,56MM,ZARV,NPM3,CM69 -prod_dir=$WL_HOME -verbose -log=/home/oracle/bits/WebLogicPatch_BulkRemove.log