Skip to main content
TrustRadius
Oracle Enterprise Manager

Oracle Enterprise Manager

Overview

What is Oracle Enterprise Manager?

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.

Read more

Learn from top reviewers

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Oracle Enterprise Manager?

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.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

22 people also want pricing

Alternatives Pricing

What is SolarWinds Pingdom?

SolarWinds Pingdom is a website uptime monitoring and alert tool, with additional reporting and Real User Monitoring capabilities. Pingdom is part of SolarWinds’s DevOps package, enabling full-stack monitoring as a service.

What is SolarWinds ipMonitor?

SolarWinds ipMonitor is a lightweight performance monitoring tool. It enables monitoring from a single console and out-of-the-box visibility, with some automation available.

Return to navigation

Product Demos

Oracle Enterprise Manager 12c: Managing Exalogic Elastic Cloud and WebLogic

YouTube

Advanced Installation of Oracle Enterprise Manager 13.2

YouTube

Backup Oracle Database using Oracle Enterprise Manager

YouTube
Return to navigation

Features

Monitoring Tasks

Various types of monitoring

8.2
Avg 7.8

Management Tasks

Various tasks required to keep systems running smoothly

7.8
Avg 7.3

Reporting

Report generation to help with system monitoring tasks

6.7
Avg 7.5

Security

Management of security aspects of system monitoring

3.5
Avg 6.2
Return to navigation

Product Details

What is Oracle Enterprise Manager?

The Oracle Enterprise Manager is an on-premises monitoring and management tool. It is designed primarily to manage the Oracle deployments in an environment but supports connectors in order to integrate with non-Oracle components. The OEM is scaled to manage enterprise-level applications, databases, hardware, virtual environments, and cloud-based systems.

Oracle’s Enterprise Manager also offers a drag-and-drop user interface, requiring minimal training or technical knowledge for usability. It also enables some automation, including generating routine reports, database backups, and problem detection and resolution, even on remote sites.

For more information visit https://www.oracle.com/enterprise-manager/technologies/

Oracle Enterprise Manager Video

Oracle Enterprise Manager Delivers Next Gen Automation

Oracle Enterprise Manager Competitors

Oracle Enterprise Manager Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

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.

Zabbix and SolarWinds Server & Application Monitor are common alternatives for Oracle Enterprise Manager.

Reviewers rate Network device monitoring and Service configuration management highest, with a score of 9.

The most common users of Oracle Enterprise Manager are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-5 of 20)

OEM great for Oracle dbs and current hardware; older vendors, not so much

Rating: 7 out of 10
October 14, 2019
MS
Vetted Review
Verified User
Oracle Enterprise Manager
15 years of experience
OEM is used to monitor Oracle databases and Exadata machines and perform routine maintenance operations like backups, statistics, etc. It's used by the dba teams for performance monitoring and usage tracking. It functions as a central repository for all Oracle databases within the organization. It has the ability to be utilized by non dba staff for quick database metrics like uptime, storage, utilization, backup duration, etc.
  • Provides a graphical interface to Oracle Database metrics (therefore one does not need to manually execute queries on a database to find information).
  • Provides a graphical interface to hardware metrics (like cpu, memory, network, i/o utilization). This is very important as it allow non system administrators to view and understand information regarding the hardware that an Oracle Database is running on.
  • Has built in features to dynamically build databases, implement RAC (cluster), implement Data Guard, and many other optional add on features to Oracle databases.
  • Has the ability to generate performance data (and other) reports that can be also be easily delivered within the organization, all through the OEM interface.
Cons
  • Information can sometimes be hard to find within OEM. There are so many different attributes that it can be difficult to find the exact area where key information can be found.
  • If OEM is running slowly, it can be hard to diagnose where the problem exists.
  • If OEM is having a performance issues and disconnects, all data is lost. This can be particularly frustrating if reports are being generated or a data guard configuration is being implemented.
  • Configuring credential setup can be very time consuming and confusing. There should be a central user that has base level OEM access for any database added to the OEM OMS repository.
  • Manually inputting credentials is very onerous.
  • As a graphical interface, not all query information is provided and therefore it can be difficult to hone a dba skill set. Since not all queries are shown, if OEM is unavailable, one will not know how to retrieve the same information directly from the database.
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.

OEM: A life saver for Oracle professionals

Rating: 9 out of 10
October 02, 2019
Vetted Review
Verified User
Oracle Enterprise Manager
7 years of experience
OEM is an excellent tool used by our organization for our day to day activities for the DBA staff. I work and assist my DBA Team to monitor, performance tune, and run the SQL analyzer for the different databases which can be controlled from within the OEM. Currently, it is being used by our IT Oracle DBA Team and without this tool, it is difficult to support our daily operations
  • Top SQL performance
  • Once place for space management for different databases
  • SQL tuning advisor
Cons
  • The dashboard sometimes is slow based on the charts and graphs being displayed. Certain drill-downs can definitely be improved in speed.
  • The central page after we log in contains too many objects which make it more cluttered and becomes difficult to view the necessary sections.
  • Login process can be more efficient encase you have just one SSO.
SQL tuning, SQL plan advisor, hint implementation, TOP SQL, database management and space management. One point source for controlling and extending all tablespaces.

Oracle Enterprise Manager - Robust Environment Management

Rating: 9 out of 10
December 12, 2016
AD
Vetted Review
Verified User
Oracle Enterprise Manager
4 years of experience
I use Oracle Enterprise Manager 11g to manage and maintain all environments used by our teams. Since it's an enterprise tool, it's used across the entire organization. OEM lets us manage users, monitor availability of environments, and deploy RPDs among many other tasks.
  • Oracle Enterprise Manager lets you control access to an environment for various users across your organization. You can define users, groups, and their credentials. You can define application roles and application policies. This is an excellent functionality which is robust in nature.
  • Oracle Enterprise Manager improves the deployment process on multiple folds using single clicks. You select an RPD, deploy the same and restart your services within a few simple clicks. No need to reach the back end and fall into a tedious loop.
  • Oracle Enterprise Manager notifies the user of any component being down in a graphical manner and points to an exact component being down. This helps in the debugging process.
Cons
  • Simple functionality like one to many mapping of users to groups could be done which would be a useful feature to a DBA/Admin while adding new users.
  • Recovery of logs needs to be more user-friendly. Whenever we face a system downtime issue, exact logs are a little difficult to find. It can get really tedious to point out the problem when looking at generic logs.
  • No cross application navigation is present to other OBIEE products. There needs to be a functionality which can navigate a user from Oracle Enterprise Manager to Oracle BI Analytics.
  • In the RPD Deployment process, there should be a functionality to deploy previously deployed RPDs. In this way, the administrator can keep a track of all previously used RPDs and it's deployments.
It is click based, intuitive and procedural. If well documented, OEM lets you do the desired task in an easy manner. On the other hand, Oracle Enterprise Manager can only be easier managing Oracle products. It may not work that well with other products from other vendors.

Why use OEM? Why not?

Rating: 9 out of 10
October 26, 2018
JS
Vetted Review
Verified User
Oracle Enterprise Manager
6 years of experience
Our organization has ~180 Oracle databases and ~200 MSSQL databases. It is used by the DBA team at this time. We use OEM to monitor our database footprint, alerting us to issues such as downtime and compliance levels. At a glance we can the status of any of our databases, uptime, performance, last backups, patch level and other non functional details such as business group, location, application point of contact, and maintenance windows.
  • Database status. Being able to see which databases are up/down, at a glance, allows us to quickly react to issues.
  • Reporting. We report on last backups, daily status, a host of metrics, and compliance levels of all our databases. With reporting we come into the office with a set of "status" reports and we know instantly if a database has issues.
  • Metrics. We have a number of KPI's and SLA's we need to meet. Metrics applied to the databases allow us to stay on top of those requirements as well as fix common issues without a DBA needing to log in to assess the issue.
Cons
  • 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.
OEM is perfect if you have a number of databases that you need to monitor. It's also great for automated jobs and reporting. However, if you have a handful of databases, OEM is overkill and you can use scripts and crontab for monitoring/jobs.

Oracle Enterprise Manager - a perfect tool for monitoring databases and for performance tuning.

Rating: 9 out of 10
December 18, 2018
Vetted Review
Verified User
Oracle Enterprise Manager
5 years of experience
Oracle Enterprise manager is being used for 2 purposes:
1. To monitor production databases for alerts against set thresholds.
2. To diagnose and drill down into details of the performance issues.
  • In OEM, the agents are installed on production database servers and they collect and send diagnostic information from databases to the OMS. The OMS compares this information with set thresholds and raises alerts in OEM. This is particularly done well as Oracle database does have lot of diagnostic information that OEM agent can collect.
  • It can monitor databases at set interval time for required diagnostic information and for error codes. It then displays that information in a GUI interface that is graphical and easy to understand. The OEM can raise alerts based on thresholds and it can send emails or input to other systems that can raise tickets or alert operations.
  • It can also run preventive actions based on alerts. This helps in reducing response time to errors and issues that can cause database downtime. There are predefined actions and DBAs can also write customized procedures to be run as preventive measures.
Cons
  • The OEM is very good at monitoring Oracle databases as they are from the same vendor and have in-depth knowledge of Oracle technology. However, improvements can be made to monitor all sorts of databases and even NoSQL databases which are now commonplace.
  • The OEM architecture can be simplified so installs and configurations can be simple and straightforward. Complex installations require a long implementation time and it increases cost of the implementation.
  • The OEM slows down response as it monitors a large number of busy prod databases. So scaling should be improved to handle large workloads.
  • The OEM should use standard TNS ports in place of non-standard ports which are often blocked in most networks. This causes delay in implementation due to violation of security compliance in most organizations.
Oracle Enterprise Manager (OEM) is suitable for a large scale Oracle DB and middle-layer product operation. Suitable if the monitoring of hundreds of Oracle databases is needed in one portal.
Return to navigation