Please download the Patch 16743790 and apply it after doing "emctl stop oms -all".
For instructions on applying the patch, please review the following document:
How to Apply WebLogic Server (WLS) Patches Using Smart Update [Video] Note 876004.1
If your OMS is installed on a NFS file system then we have a known issue addressed in
12c Cloud Control Performance: Rendering of Cloud Console Pages is Very Slow when OMS is Installed on NFS (Doc ID 1404077.1)
Also you can do the generic UI tuning as per below doc
12c OEM: How To Set The Large Concurrent UI Load to Improve the Console and OMS Performance (Doc ID 1510981.1)
Thanks Rahul. I figured out an issue with my VM settings. They were not kind of meeting certain pre-requisites mentioned in the Installation guide. I edited the virtual machine settings to contain 2 CPU cores, 8GB RAM post installation of OEM owing to slow response times from the server. Also, prior to installation of the Oracle DB, I had the user group as dba instead of oinstall. I have now associated the oracle user to the oinstall group instead of dba. Now, I have powered on the virtual machine and started the database and the listener. Now when I try to launch the OMS service, I am not able to get the Management server up and running. The logs show the error on "PolicyStoreContainerNotReadyException" and says 'Failed to search audit definition for component JPS. Reason: oracle.secutiry.jps.service.policystore.PolicyStoreContainerNotReadyException. Kindly let me know what should I do to get the OMS up and running.
The issue is now resolved. I restarted the database and listener
Restarting the database:
1. sqlplus "/ as sysdba"
2. sqlplus "/ as sysdba"
Restarting the listener:
1. lsnrctl stop
2. lsnrctl start
ReStarting the OMS
1.middleware/oms/bin/emctl stop oms -all
2. middleware/oms/bin/emctl start oms
And this time it worked!!
The response from the webserver was also good.