WLS 12.1.3.0.0 - Applying Patch 18412312: OVERLOAD PROTECTION IS NOT RESTARTING MANAGED SERVER

WLS 12.1.3.0.0 - Applying Patch 18412312: OVERLOAD PROTECTION IS NOT RESTARTING MANAGED SERVER

- Download and unzip Patch 18412312 (p18412312_121300_Generic.zip)

$ unzip -d PATCH_TOP p18412312_121300_Generic.zip

- Set ORACLE_HOME where WLS is installed

- Stop MT services including Admin & Managed Servers

- Run opatch apply

$ cd PATCH_TOP/18412312

$ opatch apply

- Start MT services including Admin & Managed Servers

- If any issues after applying patch and rollback is required, run 

$ opatch rollback -id  18412312


- Restart MT services including Admin & Managed Servers

Related Posts:

WLS 10.3.6 - Applying Patch 18412312: SU Patch [SY38]: OVERLOAD PROTECTION IS NOT RESTARTING MANAGED SERVER

WLS 12.1.3.0.0 - Applying Oracle WebLogic Server Patch 21983457: WLS PATCH SET UPDATE 12.1.3.0.6

Applying Patch 20715966: JDEVADF SECURITY PATCH UPDATE 11.1.1.7.0 (CPUJUL2015)

Applying Patch 20715966: JDEVADF SECURITY PATCH UPDATE 11.1.1.7.0 (CPUJUL2015)

Applying Patch 20715966: JDEVADF SECURITY PATCH UPDATE 11.1.1.7.0 (CPUJUL2015)

- Review and download the latest version of OPatch to 

a) For Standalone JDeveloper/Standalone WLS install type: Download the latest version of OPatch(11.1.0.0.0) via BUG 5912518
b) b) For OUI (WebCenter/SOA/Classic/etc) install type: Download the latest version of OPatch (11.1.0.8.3 or higher) via BUG 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

- Validate the executables in system PATH like 'which opatch', 'which unzip'

- Ensure Perl is 5.00503 or higher by sourcing ORACLE_HOME and running 'perl -v'

- For standalone Jdeveloper install or standalone WebLogic install types make sure that WLS server is stopped.


Applying Patch

1. Unzip the patch 20715966 zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p20715966_111170_Generic.zip

2. cd PATCH_TOP/20715966/oui

3. Apply patch (Take cold backup as applicable, recommended though not mandatory)

  i) For OUI HOME, run opatch apply

 ii) For standalone JDeveloper Home, run opatch apply -jdk <jdk_path> -jre <jre_path>


4. If Patch is successful, restart MT services - Admin & Managed Servers for OUI Home, Restart Jdeveloper and Integrated WLS for standalone Jdev Home. 

5. Clearing tmp directory recommended post patching and before restarting services.

For standalone JDev Home - 

Default location of tmp => [JDEV_USER_DIR]\DefaultDomain\servers\DefaultServer\tmp\* 

For OUI Home - Default location of tmp =>   

[MW_HOME]/user_projects/domains/[DOMAIN_NAME]/servers/[SERVER NAME]/tmp/*


Patch rollback

If patch fails for some reason, rollback the patch and restart MT services.

$ opatch rollback -id 20715966 -jdk <jdk_path> -jre <jre_path>

Clearing tmp directory recommended post rollback before restarting services.

For standalone JDev Home - 

Default location of tmp => [JDEV_USER_DIR]\DefaultDomain\servers\DefaultServer\tmp\* 

For OUI Home - Default location of tmp =>   

[MW_HOME]/user_projects/domains/[DOMAIN_NAME]/servers/[SERVER NAME]/tmp/*



Related Posts:

FMW 11.1.1.7.0 - Applying Patch 18182516: UTF-8 CHARACTERS E3 E80 E81 NOT RECOGNIZED PROPERLY BY B2B

FMW 11.1.1.7.0 - Applying Oracle Jdeveloper Patch 20265562: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 19890682 14047857 16632043