Skip to main content
Oracle Enterprise Manager

Oracle Enterprise Manager


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
Recent Reviews

OEM rocks!

10 out of 10
March 26, 2019
We use Oracle Enterprise Manager including the Diagnostic and Tuning Packs to monitor and administer over 200 production and …
Continue reading
Read all reviews


Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 16 features
  • Automated alerts and notifications (14)
  • Multiple Server Monitoring (14)
  • Performance data reports (14)
  • Administrator access control (14)
Return to navigation


View all pricing

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


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

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

20 people also want pricing

Alternatives Pricing

What is Atera?

Atera has harnessed AI to power their Remote Monitoring and Management (RMM), Helpdesk, Ticketing, and automations platform—streamlining organizational IT management at scale with the proprietary Action AI™ solution. Atera's IT Copilot augments existing tech capabilities with AI auto script…

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.

Return to navigation

Product Demos

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


Advanced Installation of Oracle Enterprise Manager 13.2


Backup Oracle Database using Oracle Enterprise Manager

Return to navigation


Monitoring Tasks

Various types of monitoring

Avg 7.9

Management Tasks

Various tasks required to keep systems running smoothly

Avg 7.4


Report generation to help with system monitoring tasks

Avg 7.6


Management of security aspects of system monitoring

Avg 6.6
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

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


View all alternatives
Return to navigation

Reviews and Ratings


Attribute Ratings


(1-20 of 20)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Oracle Enterprise Management is our central management tool of the whole Oracle inventory. We use many features except Cloud Pack and Data Masking pack.
  • Enterprise Monitoring
  • DB provisioning and patching
  • Exadata Management
  • Security subsystem, supporting integration with other PAM products
  • Offer more MGMT views to retrieve needed information
  • Log management, including one-click download of procedure activity log,
  • Support of record management based on admin group, e.g. display incidents based on admin group, save incident records based on admin groups
  • Better support of cross server OEM migration (OMS, repository DB), mostly on post tasks, such as mass promoting targets, mass transfer target properties
  • Better emcli support for mass automation, such as agent cloning
  • Better EM dashboard features to create needed reports
  • Future integration with DEVOPS tools, such as Terraform, Ansible, Bitbucket, K8
  • OEM features can be expanded to support central DB management, such as integrated RMAN catalog, TDE key catalog, etc. Currently, you need a separate DB to handle.
  • Support built-in patching scheduling and auto notification feature
In short, Oracle Enterprise Manager (OEM) is designed for frontline DBA rather than DBA managers who want to get ad-hoc information. For frontline DBA, it is easy to see an incident and take actions. Almost all details are captured and organized in tabs. That is beautifully done. As a manager, it is hard to get a complete picture of operational status based on his selection criteria. In large EM deployments, mostly, targets are organized by using admin group. Besides, the incident records displayed by clicking on [Get Results] cannot be saved as Excel sheet. If that can be one, we can use Excel features to compare. Besides, OEM is inconsistent in log management. Certain results can be saved in offline format and certain cannot. It is extremely important to save procedure activity log in an offline html that preserves the format for internal auditing requirements. This proves a task is done successfully in OEM.
Score 9 out of 10
Vetted Review
Verified User
Oracle Enterprise Manager is the right tool for the job for us, due to our needs for monitoring a highly-regulated production environment. We leverage Oracle Enterprise Manager across our entire organization for the full automation lifecycle of common database management tasks. This allows our IT team to focus on delivering value and avoiding toil.
  • Seamless application of security and feature/fix patches
  • Elegant rolling updates to ensure little or no downtime
  • Anomaly detection to quickly alert ops team to issues
  • Upgrade speed can sometimes be slow and unpredictable
  • Occasional anomalies that cannot be automatically rectified and require human intervention.
  • UI can be sometimes buggy and slow
For large organizations with many Oracle database projects across the fleet, there is no better choice. Otherwise ops teams will be doomed to maintain homegrown scripts that are error prone and would not scale well across many databases. Having a single pane of glass for DB management has been a real paradigm shift made possible by Oracle Enterprise Manager.
Score 9 out of 10
Vetted Review
Verified User
Oracle Enterprise Manager is primarily used by the database team as well as two other departments for monitoring purposes. For me as a DBA, it helps me to get a holistic picture of the databases and their components in the organization. It makes it easy managing and monitoring the databases easier. Also, in case of incidents, we get notified instantly, along with repeat alerts, which helps to address and resolve the issues sooner.
  • Helps to see what databases are not up to date with respect to patches
  • Tablespace usage alerts help to avoid running out of space
  • End-to-end database component management is very simple
  • Performance home for instances at times misses data when it transitions from one instance to another
From my experience, I believer Oracle Enterprise Manager makes life easy for the management of all the databases and their components over URI as well as for automating certain management tasks using the command line. It's a blessing, especially when there are hundreds of databases with different database versions (because of legacy applications) running.
Score 8 out of 10
Vetted Review
Verified User
Oracle Enterprise Manager is being used at a large federal department to manage, monitor and troubleshoot the production and other NPE environments. Target types include Siebel, Oracle Fusion Middleware (OBI, BIP), and Tomcat. It is used department-wide.
  • Monitors the availability of Siebel.
  • Integrates with Oracle Support to help troubleshoot issues by automatically looking up errors codes against known bugs.
  • Performs configuration management of targets, allow the team to spot easily anomalies.
  • Providing true RBAC when integrating with Active Directory. Some objects must be owned by individuals instead of AD groups.
  • Incidents can only be assigned to individuals instead of teams, for example, the Siebel team or the Oracle DBA team, which could be an AD Group.
  • Does not support newer versions of Microsoft IIS on Windows2016 Servers.
Well suited to monitor the Oracle application stack, right from Exa-systems, databases and oracle applications.
Not so much support for third-party applications. Not great for monitoring network traffic on a host, I.E. top-talkers.
Score 9 out of 10
Vetted Review
Verified User
I use Oracle Enterprise Manager (OEM) on a daily basis. I use it for individual database/cluster monitoring and enterprise wide for our entire client base.

It's great for monitoring multiple systems and has a wide variety of pre-built metrics. It can be used for deploying scripts to our entire system. It's easy to use and critical for technical users as well as non-technical users.
  • Displays visuals of database health
  • Shows internal data structures (tablespaces, objects, users, etc)
  • Monitors database health
  • Can be used for deployment of PL/SQL and other scripts
  • It can be very buggy, sometimes preventing jobs from running
  • It can miss errors and lead to database outages
  • Can be slow during updating of internal settings
It's great for managing many database systems, from hundreds to thousands of systems. If your system has few databases, it may not be suitable. It also monitors other non-Oracle systems.

If you have small databases that are lightweight and are low-maintenance, OEM may not be useful. For larger companies, it can be very useful.
Score 10 out of 10
Vetted Review
Verified User
Oracle Enterprise Manager (OEM) is being used in dev/test and prod environments. It is widely used by DBAs for monitoring and day-to-day operations. It is also widely used as the dashboard console for the managers to have an overview of the database systems.
  • Dashboard: Options to choose Home Page. Best for DBAs, best for new users and etc. I selected "best for DBAs" as my Home Page. It gives you the status (up or down) of all the databases registered. If you click each database a nice diagram shows up. On the left, you will see Load and Capacity, Incidents and Compliance, Recommendations for findings and SQL tuning, Last Backup and if there are any Jobs running.
  • Performance Home: Overview diagram of host average runnable processes, average active sessions, throughput, I/O, parallel execution, services. It also provides additional links to top consumers, instance locks, duplicate SQL, instance activities and SQL response time.
  • Top activity is another nice feature: details for 5 minute intervals. It further provides top SQL and top session. This is my go-to page for database performance tuning. You click the top SQL to get details on the "troubled" query, statistics, activities, plan and tuning history.
  • SQL tuning advisor is another nice feature: you can schedule a job to run the SQL tuning advisor or run it immediately.
  • AWR Report: when we start having DB performance issues, we run AWR a pare of snapshot reports and then compare them with a baseline report to nail down what has caused performance degradation.
  • Security: users, roles, profiles, auditing settings, data masking, and subsetting, data redaction, transparent data encryption, data vault, label security, virtual private database, and enterprise user security.
  • Scheduling jobs: we have 70 jobs running every day - backup, space, monitoring and sending alerts to email.
  • 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.
It is a great tool for DBAs and management with limited access. In my opinion, this is not very useful for developers. DBAs can't seem to daily work without OEM.
Osman ŞEN | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
The best tool for the Oracle environment. Sparc CPU has a high frequency that Intel can not provide. Using this CPU has some cost benefits on Oracle DB licenses. With the ZFS and the Logical Domain combination, you get extra flexibility. It can be hard for some admins to use CLI to manage it. In that case, Oracle Enterprise Manager will be your indispensable tool to cope with this problem. This tool will provide you with ease of administration and visibility in both hardware and software layers. Performance, hardware, and software monitoring, automatic case submitting at problems, new ldom installations, live migration between ldoms, ZFS snapshot management and similar operations in the Web-based graphical interface will provide you real comfort.
  • If you use Oracle (Sparc) environment, This software is essential.
  • Deep visiblity to Hardware, Software and Performance.
  • Manage easily even you are not familier with this enviranment.
  • Not yet.

If you have an Oracle environment. It is necessary.

You will save time at admin operations. You get comfort with well designed GUI. You will have a great visibility at its topology, hardware and software.

You can advanced operations like firmware os update, live migration on LDOMs, snap operations at ZFS, etc easily. Auto case submit.

But If you do not have it does not suit you.

October 15, 2019

OEM is the best!!!

Ken Turner | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We are using Oracle Enterprise Manager to manage all of our databases and manage all jobs within the department. We also use it for SQL tuning, AWR and running SQL on many databases at one time.
  • Allows you to manage multiple databases in one GUI.
  • Allows you to run jobs on multiple databases at one time.
  • Helps you maximize Oracle Database tuning and SQL tuning.
  • Also, helps manage dataguard within multiple databases.
  • Notification emails. Notifications are sending out emails for failed jobs 7 days later of the same error of the same job.
  • Being able to have redundancy for Oracle Enterprise Manager. This is way too complicated to get set up and has too many problems getting it set up. The documentation is not very good. Just making it more user-friendly and easier to install.
  • Starting OMS takes to long. Depending on the machine it can take up to 10 minutes for OMS to start up.
Oracle Enterprise Manager is well suited if you have to manage multiple databases. It helps with job configuration, not only for the database but also for each database host. It allows you to run different types of jobs on each host and you can run pl/sql jobs or host scripted jobs from each server.
Score 7 out of 10
Vetted Review
Verified User
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.
  • 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.
Score 9 out of 10
Vetted Review
Verified User
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
  • 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.
Mohan Hundre | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
In our company, I am using Oracle Enterprise Manager (OEM) for the best monitoring tools. Oracle is managed by database-related activities, like checking database connectivity, database storage, database spaces... Etc.
Currently, I am using OEM tools 13c, and I previously used the 11g and 12c version of Oracle Enterprise Manager.
  • It is used to provide more than others as compared to price.
  • Basically, it is used to check our database connection.
  • Oracle provides quick support on any issue.
  • It manages various activities, and handling is easy to use for good GUI functionality.
  • Some features are complicated for new users to understand on my first attempt.
  • There is some time connection loss issue.
  • They need to provide better features in some aspects.
As per how it is used in my company, it is used for smarter work in the organization. It's proved to be time-consuming to use other monitoring tools to check any health issue.
Score 8 out of 10
Vetted Review
Verified User
We use this to monitor all our Oracle databases and Linux VMs along with Oracle OVM. Also used for deep dive into database performance and to investigate SQL performance issues.
  • Able to setup blackouts for all or parts of what is monitored.
  • Also used to send issues to ServiceNow.
  • Using it to incorporate all our crontab jobs into Jobs.
  • Able to view history and use AWR repository to compare to current execution plans.
  • Monitoring templates. They give way too many bogus alerts. We had to remove 90%
  • Seems that every patch lately introduces new bugs, so it's not tested well
Suited if you have lots of databases to monitor. Now, all of them are in one spot with Oracle Enterprise Manager. Very good drill-downs for running SQL. We use it a lot on SQL performance issues.
Score 9 out of 10
Vetted Review
Verified User
Oracle Enterprise Manager is being used by the database administrators in the IT department. It servers as an important tool and interface for database monitoring.
  • It manages all relevant targets (hosts, Oracle databases, and listeners) in one place
  • We can use it to quickly drill down an issue to its detail
  • In addition to monitoring and performance tuning, it can be used to present information effectively
  • It relies on a monitoring agent to be installed on monitored target hosts, and that dependency can be problematic at times
  • The performance of Oracle Enterprise Manager itself can be slow
Oracle Enterprise Manager is well suited for monitoring multiple oracle database, especially RAC databases (where multiple hosts are involved in clusters). It is probably an overkill if just for one or two single instances. It is also good at troubleshooting complex performance issues with queries, when an effective time-based monitoring on multiple facets of the system (CPU, memory, I/O, and SQL plans, etc) is needed. It is a good tool to present such information as well, in a well laid out, graphical manner.
March 26, 2019

OEM rocks!

Score 10 out of 10
Vetted Review
Verified User
We use Oracle Enterprise Manager including the Diagnostic and Tuning Packs to monitor and administer over 200 production and non-production Oracle databases on about 30 Linux servers. These databases are used across our entire company and range from 50 GB to 30 TB. We have SAP, Hyperion, and homegrown applications using the databases. OEM allows me (a single Oracle DBA) to maintain a large amount of complicated database including Oracle RAC, Oracle single instance, and Oracle Dataguard standby databases. It also provides monitoring of servers, storage, network, listeners, and agents.
  • OEM is fantastic at monitoring databases and servers. It is a single place to check the enterprise-wide database, listener, agent, and server status. You can set thresholds on many metrics including space at the operating system level and the database level.
  • OEM can easily push agents to remote servers.
  • Once an agent is deployed to a server, it can easily be configured to monitor the server, databases, listener, and agent with various thresholds on many metrics. Alerts can be viewed on the OEM Console or via email.
  • OEM can be used to administer databases. Any function that can be done in an SQLplus command line can also be done in OEM. A few such tasks are tablespace management, user management, table/index/object management, etc.
  • OEM can be used to implement Dataguard Standby databases.
  • OEM can be used to monitor backups in real time.
  • OEM can be used to monitor SQL real time. The Diagnostic and Tuning Packs allow you to create SQL Profiles for slow SQL that can increase run times by 1000s of percents.
  • There can be some bugs in OEM. Usually there is a workaround, but sometimes you might need to install a patch.
Oracle Enterprise Manager (OEM) is well suited for administering and monitoring Oracle databases. While it can also monitor other types of databases, it is not as robust in doing so.
Score 9 out of 10
Vetted Review
Verified User
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.
  • 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.
October 26, 2018

Why use OEM? Why not?

Joseph Szupiany | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
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.
  • 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.
Score 8 out of 10
Vetted Review
Verified User
We had used Oracle Enterprise Manager for our clients based out of the US, Canada, and Europe as an on-premise tool to manage all the major Oracle products used by the customer. Some of the Oracle Product Suites which the customer used were Oracle Database, Oracle SCM, Oracle HCM and Oracle EBusiness Suite. The enterprise manager was one single platform where all the customer's Oracle deployments could be managed. It helped us in managing Oracle EBIZ Application Management, Database Management, Database Performance Management and new installations and upgrades.
  • Enterprise Manager Management Connector is one wonderful tool to connect to any third party applications. Some advanced notification methods are available for use cases varying between simple to complex in nature.
  • Automatic Workload Repository (AWR) captures a snapshot of the operational statistics of the database at regular intervals. This helps in diagnosis in case of any issues going forward.
  • Enterprise managers Oracle application management suite helps with automating all routine operations which would normally consume good man hours.
  • Oracle Application Management Suite pro-active monitoring of various activities with the business application.
  • Licensing agreement is complex in nature probably due to its enterprise-wide reach. It needs to be simplified to an extent.
  • It is recommended to have all the patches and solutions required for the enterprise manager usage, as any missing patches may cause hindrance going forward.
Oracle Enterprise Manager is well suited to an organization using multiple Oracle Product Suites and they want a single platform for managing the different Oracle products as well as any third party products. OEM has standard plugins available which will enable easy integration with third-party products. Enterprise Manager may not be well suited for an organization which may not be primarily using Oracle products.
Candy Carrizales | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We use Oracle EM to monitor multiple metrics across several of our databases including running processes, active sessions, tablespace and storage utilization, blocking sessions, and several other critical metrics. Oracle EM solves the issue of having to monitor different databases using scripts or linux reporting tools or mail alerts that can pass on cryptic data, but instead simplifies messages that indicate an issue with the database or database connections.
  • Creates visuals and graphic indicators for monitoring critical database operations and states.
  • Easily identify problematic connections, performance issues, blocking sessions, and identify sql code or scripts that are degrading database performance.
  • Easily display AWR reporting or ASH analytic's with a few clicks.
  • Easily set up jobs with Oracle scheduler, which you would have to otherwise script directly on the database.
  • Connections to targets can become lost or dropped, resulting in the application not doing anything when clicking on a link, with no type of indication of what the issues is.
  • Log outs from the console sometime do not complete, and users remain logged in, even after closing the browser session.
  • The timeout function in the console has always been problematic, causing me to have to change the time out setting in the config file, whereas the option to disable the time outs on the console when the option comes up does not work. Selecting the option to disable timeouts still causes idle sessions to timeout.
Oracle EM is perfect for monitoring database performance, alerting dba's of critical thresholds, setting up simple tasks using oracle scheduler, identifying problematic scripts or code that are degrading database performance, identifying and resolving blocking sessions and locking sql, and many other database performance monitoring tasks. Where it is a little less suited is configuring backups with non oracle backup systems such as NetApp, monitoring end users connections to the database, some administration tasks such as resizing the SGA or adding datafiles to tablespaces, or changing database configuration files such as the pfile.
David Fowler | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We monitor databases, schedule RMAN backups, provision databases, patching, user management, space management and run reports in BI Publisher.
  • Gives a big picture view your Oracle infrastructure, and plug-ins for SQL Server, IIS if needed.
  • Manages jobs in each instance using dbms_scheduler package.
  • Integrates with Oracle support for patch download, applies patches.
  • Manages space in tablespaces, data files. Alerts set to your comfort level for warning critical thresholds.
  • Interface clunky at times. Some space management is faster in SQL Developer DBA tool. Their free tool works well.
  • Setup of default page gets lost at times. Bug?
  • Managing a script run across databases. The default is backwards. SYSDBA should be the default. Not normal.
Job management, provisioning, patching, space management
Advait Deshpande | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
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.
  • 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.
Return to navigation