Oracle’s Enterprise Manager is an on-premises monitoring and management tool. The console is designed primarily to manage other Oracle products, it but can integrate to manage non-Oracle components as well.
Datadog is good at collecting metrics, monitoring, and alerting; whereas, with Oracle Enterprise Manager, in addition to all that, we can manage the infrastructure as well as automate certain fixes.
OEM is better at monitoring applications, while SolarWinds is better at monitoring the underlying infrastructure such as networks, switches, and routers.
Foglight is great, but expensive. It has great monitoring like OEM, but can negatively impact database performance. OEM is better than Foglight because it is a native application from OEM and has features that Foglight doesn't have.
Being an Oracle shop using Oracle Database and MySQL, management console from Oracle was a better choice than IBM or Microsoft even though we do use Microsoft Azure and storage/servers from IBM (on-prem).
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 …
I am using Nagios Enterprise monitoring tool also, but as compared to Nagios, Oracle Enterprise Manager is best for our company. Nagios is very weak in some aspects.
Have not tried via Oracle Enterprise Manager, but CommVault is used by corporate for all backups of storage. However, it is just using Ansible to kick off RMAN jobs.
Toad for Oracle is more suited for individual users who have a strong focus on database development, and it is not as comprehensive as Oracle Enterprise Manager. While it is quite decent in logical database layer tasks, such as schema objects and SQL, it lacks visibility into …
OEM Cloud Control base version is free to use if you have licensed Enterprise Edition of one of the Oracle Product. It's sophisticated single point of control, we have used other monitoring products such as Veeam but none of the products have all the features packed together …
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 …
It is much simpler to install and configure as compared to Spotlight and Solarwinds. Oracle Enterprise Manager measures performance diagnostics accurately and raises alerts and takes preventive actions. Other products can not take preventive actions even if they raise alerts. It …
Oracle Enterprise Manager suited our requirement as the clients were using multiple products of Oracle. They were using several instance of oracle implemented at different geographical locations each in Europe, UK, Canada, and USA. So Oracle Enterprise Manager was best fit for …
We have not used any other products to monitor and/or manage our oracle instances. We have always used Enterprise Manager, although we did use a previous version (11g Grid Control), right around the time I arrived at my position. I upgraded to 12c Cloud Control with the …
SQL Developer DBA module allows user, space management, SQL Tuning, ad-hoc queries, and schema management. Great free product supported and enhanced from Oracle.
Oracle Enterprise Manager is easy to install, use and extend the capability of. It supports many Oracle products, which is what it is used for in my company. We selected OEM for its ease of use, intuitiveness and robustness.
OEM is very well suited for all Oracle products, especially Oracle databases and Exadata machines; even not Oracle hardware, it is very good and displaying high level details. OEM is not well suited for older hardware vendors like AIX, HP-UX, DEC/Digital, Microsoft (sql server). This is a big negative as most large companies have a heterogeneous environment with many different vendor hardware and (database) software products.
Monitoring Templates: There are out of box monitoring templates for each target types, you can customize them or use them as it is.
Administrative Groups: This is a relatively new feature in OEM Cloud Control. This lets you create and manage your targets and monitoring templates smarter and with less re-work.
DB Monitoring: There are so many cool DB monitoring features and visual graphics, that it can be used by both DBA and functional people to see what's going on in the database.
Bugs. Every version we upgrade to has a number of bugs. Some stop us from rolling to production OEM (we have a sandbox OEM), some are simply annoying. If I could improve on one thing, it would be for better QA from oracle before releasing each version.
Flash. I'm told that they are moving from Flash to Jet in version 13.3 and beyond (we are on 13.2 currently). That change cannot come soon enough. The OEM pages load SO slowly due to Flash.
Hierarchy Groups. OEM allows five Hierarchy groups. A Hierarchy group allows a top down metric/rule roll out. However, they limit you to five. I'd like to see them open that up, so that we can have any number of custom groups.
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.
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.
Being an Oracle shop using Oracle Database and MySQL, management console from Oracle was a better choice than IBM or Microsoft even though we do use Microsoft Azure and storage/servers from IBM (on-prem).
We are a 7x24 shop. Oracle Enterprise Manager Cloud Control helps us meet that objective by proactively warning us before issues cause down time. Things like disk space, archive log issues or temporary table space issues.
Spreading the use of this tool outside of the DBA group has allowed us to not hire additional personnel for those teams. Over time, as folks have retired from our operations team, we are not replacing them. Instead we have used OEM Cloud Control to automate tasks.
We also now have the tools to measure up-time by using specific measurements inside of OEM. This allows us to report real numbers to management.