The majority of Enterprise Manager 12c Cloud Control agent installations are pretty straight forward, just do the usual checks, ensuring firewalls are open etc. and then deploy from the EM console. The Windows installations are not as straight forward these days, as the deployment method uses SSH connectivity which requires the installation and configuration of Cygwin as a
Now that Oracle Enterprise Manager Cloud Control 12c Release 3 (aka EM12cR3!) has been out for a few weeks, I decided to brave it and upgrade our Production stack today. In this post, I’ll be upgrading an EM12cR2 (12.1.0.2) installation which consists of two OMSes, running on Linux x86-64 (RHEL5) which uses an 11.2.0.3 database management repository.
Enterprise Manager Oracle Management Server (OMS) installations generate huge amounts of log and trace files under the covers these days, and although the logs are rotated out-of-the-box, they’re not automatically deleted. Over time (as I was reminded again today 🙄 ), these logs can amount to a large portion of your disk space being used.
Generally speaking, the Java heap memory utilization for your Oracle Management Service (OMS) should be averaging at under 75%, and anything over this could mean the Garbage Collection starts impacting the performance of your Enterprise Manager experience. If you’re using the “out-of-the-box” notification rules, then an OMS suffering such symptoms may start churning out events like this: