Sometimes applying Tech Stack patches lead to bugs or issues which we know. This is one such instance where the OPMN was failing to start after applying latest ETCC patches. So let us see in detail:
I have applied latest ETCC patches which includes patches for WebTier, 10.1.2.3, WLS etc. Once they are applied, opmn was failing to start and when I checked the OPMN log file, I have found the below error in it:
[opmn] [ERROR:1]  [ons-secure] Connection server SSL set credentials failed (43084)
[opmn] [ERROR:1]  [ons-secure] SSL initialization failed
Oh! But wait.. I don’t have SSL or TLS configured in my environment but why is it complaining about SSL here? So apparently! after applying latest security patches of Oracle Process Manager and Notification Service (OPMN) and Oracle HTTPS Server (OHS) 220.127.116.11 components for Oracle E-Business Suite, this is expected.
Why does it happen?
The FMW no longer accepts the usage of certificates signed by MD5withRSA and requires using SHA256withRSA or better. So even though you don’t use SSL or TLS in EBS, you still have to create self-signed certificates and import them to wallet.
The detailed steps are present below:
Prerequisite Steps to Configure Oracle Fusion Middleware 18.104.22.168 Components for Oracle E-Business Suite Release 12.2 Before Applying the July 2019 and Later FMW OSS Security Patch (Doc ID 2555355.1)
Happy Patching CPU and ETCC patches 🙂