OMS 13c was responding slow, happen to hear the same complaint from fellow DBA's. I was like, I wish there was some turbo or magic button to make it fast, jokes aside. Started drilling down into logs, happen to find strange errors from the OMS alert logs as mentioned below:
Look up for SIGTERM in the alert log, to be more specific it is signal termination.
####
Fix:
####
[oracle@sajidserver ohs1]$ pwd
$OMS_HOME/gc_inst/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/ohs1
Take the backup of the file.
[oracle@sajidserver ohs1]$cp httpd.conf httpd.bkp_date
[oracle@sajidserver ohs1]$ vi httpd.conf
look for mpm_prefork_module and mpm_worker_module, they will look like below.
Change the highlighted line in yellow to /u01/locks. Make sure you have created the locks directory in /u01 with oracle account and 775 permissions. Save the changes and exit the file.
Last and final step bounce the OMS.
[oracle@sajidserver logs]$ emctl stop oms -all
[oracle@sajidserver logs]$ emctl start oms
I have seen the OMS was responding fast enough. I happen to go through Oracle Metalink note (Doc ID 2117861.1), the same fix even works for OMS 12c too. Hope it will be even helpful to you folks too.
