EBS 12.2 Managed Servers not starting after applying Apr 2019 CPU

0
152

Applying the latest CPU patches for all the oracle products is very important. EBS is no exception and it is strongly recommended to apply the latest CPU patches. Needless to say, these patches need to be thoroughly tested before applying on PROD.

I have applied Apr 2019, CPU on EBS 12.2.8 instance and to my surprise after completing the ADOP patching, the managed servers are not starting i.e. OACORE, OAFORMS etc. The logfiles show the error as below:

<> <> <> <1562353039890>  <Server subsystem failed. 
Reason: weblogic.utils.NestedRuntimeException: [Security:090467]
problem with
connection filter weblogic.utils.NestedRuntimeException:
[Security:090467]problem with connection filter at
weblogic.security.SecurityService.initializeConnectionFilter(SecurityService.java:338

So let’s see why we are unable to start the managed servers post APR 2019 CPU and how to fix it.

Firstly, Oracle Introduced Connection Filters from Apr 2019 CPU in EBS. Please read the documentation below to ensure you follow the guidelines and change the settings of Context File and config.xml accordingly. See section : Managing Configuration of Web Application Services

https://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T589913.htm

Coming to the issue, there are 2 patches that have been mentioned in APR 2019 CPU Note: Oracle E-Business Suite Release 12 Critical Patch Update Knowledge Document (April 2019) (Doc ID 2514102.1)

One is 29224724 and other is 29524595. In case you have applied the Patch 27294892 then you need to apply 29524595 which I believe creates the necessary libraries needed for the new WebLogic Security Connection Filters. I applied 29224724 first and realized that I applied the wrong one. Once I applied the 29524595 patch, the issue has been resolved and I am able to start the managed servers.

LEAVE A REPLY

Please enter your comment!
Please enter your name here