With EMCDC 13.5 adding a new OMS may fails with the following error
SEVERE: Exception occurred while securing OMS:
java.io.FileNotFoundException: /ora01/app/oracle/product/gc_inst/user_projects/domains/GCDomainStby/config/fmwconfig/components/OHS/instances/ohs3/ssl.conf (No such file or directory)
The issue turns to be related to the nodemanager not starting fast enough.
The workaround may be to increase the shape of the VM running the second OMS and/or, before trying again to:
- Cleanup the OMS directories on the 2nd OMS
- Remoive the agent from the OMS
- Make sure there is no entry left in /etc/oragchonelist and in the local inventory
- edit the file $ORACLE_HOME/sysman/omsca/scripts/wls/jrf.py on the primary OMS to change
dd
From:
import sys
import os
. . .
startNM(nm_user, nm_password)
#start the Managed Server
To:
import sys
import os
import time
. . .
startNM(nm_user, nm_password)
#start the Managed Server
import time
time.sleep(1800)
And edit
tep-4: Edit the <$ORACLE_HOME/bin/omca to add -nocleanup at the end of the last line