AWS Systems Manager vs. Oracle Enterprise Manager Cloud Control

When you have a process running in aws that needs to copy files to group of instances as part of the process Installing software on a group of machines Adding Cloudwatch agent to instance.

Incentivized

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

• Copy files to a group of instance with particular tag
• Enable CW agent and push metrics to CW
• Easy to install software in a group of instances.

Incentivized

• 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 the Search feature improved a bit more.
• UI is little bit confusing initially

Incentivized

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

Incentivized

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.

Incentivized

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

Incentivized

• Reduced team's time spent on EC2 management
• Patch management
• Remote access

Incentivized

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

Incentivized