OpsCompass vs. Oracle Enterprise Manager

Our AWS Cloud was a perfect fit for OpsCompass. We needed a better method for understanding the size/extent of our Cloud--rather than the manual approach we'd been using. It's saved us a lot of time, and allowed us to delay adding additional heads for at least six to nine months. It also gives us a better/faster grasp of potential security issues - we see them right away, and we can assess each issue far faster than ever before. When we expand to Azure, Ops Compass will be able to do the same thing for us. (We have no plans to expand into Google Cloud Platform, but Ops Compass works well in all 3 clouds, apparently.)

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.

Incentivized

• Quick inventory of all my cloud resources
• Detects changes to my cloud resources--including the source of the changes (user or system)
• Cost impacts of changes to my cloud infrastructure

• 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.

Incentivized

• I would like to see more integrations to help surface alerts. Slack would be great, as an example.
• An imbedded tour or onboarding would help our new users, but overall, the product is pretty easy to figure out

• We also use OEM to monitor SQL Server. However, OEM only provided limited features for SQL Server. It would be nice if we can schedule backup jobs for SQL Server in OEM.
• The ability to run SQL queries. You can't run queries in OEM. I have to go to SQL Developer or SQL PLUS to run. queries.

Incentivized

It's great! It does everything and anything you would want it to do. It can monitor things which doesn't comes out of the box by adding plug ins to it, for example, you can even monitor Oracle GoldenGate Replication by adding a plug-in to OEM Cloud Control.

Incentivized

I still rate OEM as a must-have tool for central management of Oracle fleet. The pros and cons of the product is prominent. Meanwhile, I also acknowledge that OEM was design about a decade ago. At that time, it did not have the landscape we have today, such as cloud, DEVOPS, machine learning, etc. I hope in future releases, the design will incorporate those features.

Incentivized

We like that OpsCompass is native, multi-cloud, and gives us a consistent method and approach to managing our security across multiple environments. It was more attractively priced and had easier, simpler deployment. It took us about 30 minutes to get it connected to both of our clouds and get a quick view of all of our infrastructure.

Kibana from Elastic is another monitoring tool that claims to provide very similar information to OEM. It seems to be an information tool rather than a tool that can actually make changes within a database. I think Kibana is more robust for hardware versus database software so it is more suited to that purpose and does to compare to the Oracle Database monitoring attributes of OEM.

Incentivized

• Our team was able to do roughly 30% more with the product. The automation helps us spot issues without a lot of manual work
• We identified changes that would have had a massive cost impact--spinning up or forgetting about infrastructure we didn't need.
• OpsCompass prevents configuration drift and maintains a healthy state across multi-clouds.

• Positive: Alerting features. Without this we would have to be a 24x7 shop with someone always manning the helm. With the alerting feature we can define levels of alerts and only get the most pressing alerts sent out.
• ROI: OEM is free, so the ROI is whatever you make of it.

Incentivized