Likelihood to Recommend
I wish I had an option to give it a 9.5 :) OEM Cloud Control is very well suited if you have a system with multiple implementations of Oracle Database Enterprise Edition. If you are willing to pay for the huge license cost which is typical with Oracle, then you will love to use OEM Cloud Control to monitor your entire ERP solution including web servers, applications, network, storage, and physical servers. It is not worth the buck if your's is a small implementation. Your DBA's should be able to work without depending on OEM Cloud Control.
Read full review
We have taken advantage of the single platform for different IT disciplines over the past few years and now we are doing more and more with the integrations. Our teams are looking at the same information which stops the blame game a lot. Their newest AIOps has been a very nice surprise as we've tried another tool for about 2 years and it required us to hire outside consultants to try and build what we needed. So far, ServiceNow found a lot of things we didn't know to look for. It's not perfect in fixing everything, but really has provided a lot of visibility and troubleshooting.
Read full review Pros Oracle Enterprise Manager is a "one stop shop" for all of our management needs. This is helpful because it minimizes the management of the management software itself. There are less upgrades and connectivity issues to handle. And there are "plug-ins" for additional products we use like Blue Medora's one for PostgreSQL. Managing administrative jobs can be burdensome in a shop with dozens of servers and databases. OEM Cloud Control makes it easy since you can view all the jobs for all servers in one place. It is easy to filter on jobs with problems or the like so that you can quickly look at the logs and fix the issues. Tuning PL/SQL is much easier using OEM Cloud Control. Most DBAs are familiar with trace files and TKPROF, but not having to do those things at a command line smooths the process out. The graphical interface makes it easier to show developers exactly what the issues are. This makes for less finger-pointing and quicker resolution of performance problems. Proactive management is easier using OEM Cloud Control. Before having the gui, I had a collection of scripts that I would have to install on each database server, then set up cron jobs to run them. When Oracle was upgraded, those scripts might have to be updated on each and every server. OEM Cloud Control has those things built in. You can choose exactly which metrics are important to you. And you can keep performance graphs up all day on a second monitor to let you instantly see when something might cause a problem. Read full review license management Integrate with other tools Dashboards Change Management - impact analysis Read full review Cons Oracle Enterprise Manager Cloud Control can do a better job in actively managing (as opposed to monitoring) non-Oracle IT components including non-Oracle database, middleware, and storage. The UI is less responsive and sometimes slow and the user experience could certainly be improved. There is also an issue with positioning as other Oracle products sometimes come with their own versions of management console so it is hard to justify paying for Oracle Enterprise Manager Cloud Control separately or as a new attachment. Read full review A lot of flexibility in the licensing options which can get overwhelming. They are just starting to get into helping with DevOps so I don't have as much experience there but it's a challenge for us. Pricing negotiations - although that can be pretty much every vendor. Read full review Usability
I wanted to give it a 10 but the heavily loaded solution makes it slow to load and refresh pages. Even bouncing the OEM Cloud Control takes around 10 mins which is quite long.
Read full review Alternatives Considered
Since OEM Cloud Control comes free with Enterprise Edition, we have mostly worked on OEM Cloud Control. I did have my fair share of experience with
. It's good and lighter than OEM Cloud Control. It sort of removes your need to even go to SQLPLUS command line most of the time. But it is way behind OEM Cloud Control in terms of features.
Read full review
We wanted it integrated with ITSM and ITBM. Prioir to that we used JIRA for agile development and SysAid for ticketing. So we started with converting SysAid. We went live with Vanilla ITSM. Then we could have a basis for ITOM. However, we needed to migrated from JIRA to ITSM. Only then we felt mature enough to examine ITOM, which required quite a lot of resources. You need networking, motoring, IT and Cyber security team members in your project!!
Read full review Return on Investment Freed up DBAs and SAs by automating much of their antiquated manual processes. We are limited by our own desire to use and learn all of the features within OEM. Read full review Eliminated a lot of manual processes with automation and sharing information across team. Cleaned up our CMDB from well below 40% accurate to well over 90%. AIOps finding anomalies and tying them to service maps. Read full review ScreenShots