Hello all,
all REFRESH/UPDATE-MOS-Jobs in EM stopped working a couple of weeks ago. The error is "Authentication Error: Please check your credentials: IO Error: Status code: 502, Reason: Bad Gateway", although no problem can be seen on the firewall, the credentials have not been changed and they work fine when used to log in to MOS manually, but throw the same error when set again inside the EM. Other credentials throw the same error.
I found MOS DocID 2998693.1 which gives a workaround for RU22 only.
We have EM 13.5.0.0.0 and therefore need to update the EM to RU22.
The EM is running in a virtual server with Oracle Linux 8.10 on an ODA.
The whole ODA was recently upgraded from 19.18 to 19.22, so the EM-repository was updated to Oracle 19.22 as well.
The readme (and “omspatcher apply -analyze” ) for RU22 (patch 36335368) states the requirement for some additional JDBC Patches for Version 12.2.1.4.0 : 35430934, 34153238 and 31657681. I looked into the readme of the first of those (Patch 35430934): This patch includes support CryptoJ FIPS 140-2 mode for the JDBC Thin Driver and “Please make sure you are using the CryptoJ version Crypto-J 6.2.5 or above”.
I found $OMS_HOME/oracle_common/modules/oracle.rsa/cryptoj.jar, which is Version 6.2.4.0.1. So no version fit.
Our JDBC Version ($OMS_HOME/oracle_common/modules/oracle.jdbc/ojdbc8.jar) is 19.3.0.0.0. . Also installed by EM 13.5 are some older Versions ojdbc5 to 7 in Versions from 11.2.0.1.0 up to 12.1.0.2.0. I found no Version 12.2.1.4.0 in the whole $OMS_HOME . So, again, no version fit here.
Can I safely ignore the warning about those three pre-RU22 patches and go on with the update to RU22 by installing just the one patch for RU22?
Or do I have to install some other stuff (and, please, which is it?), then apply those three pre-RU22 patches and finally go on with the update to RU22?
Thanks in advance!
Susanne.