Reviews (1-17 of 17)
- 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 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.
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.
- 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.
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
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.
- 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.
- 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.
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.
- 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
- 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.
- 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
- 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 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.
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.
- 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.
- 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.
- 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.
- 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 Scorecard Summary
Feature Scorecard Summary
About Oracle Enterprise Manager
Oracle Enterprise Manager Technical Details