Komprise is the database development and management solution from the company of the same name in Campbell, California.
N/A
Oracle Enterprise Manager
Score 7.0 out of 10
N/A
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.
As any other archiving solution, it is very well suited for environments with a large footprint of unstructured data (CIFS / NFS shares for user data) with a large amount of unused/old files and a need to keep those unused files for long term. In our scenario, due to some legal and contractual constraints we need to keep these files for 15 years. Archiving is a good choice to move the unused files to a cheaper storage tier, both on-prem or cloud.
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.
We have used Veritas Enterprise Vault in the past, and besides its being a well-known player on the data archiving market, their tool is far more complex to implement, to manage and to keep working. Komprise is very robust and also very easy to implement, as most part of the job is done on Komprise side. The management console is delivered through a public URL as a SaaS platform. You only need to deploy a few VMs for scan/archiving/user access, which they call "Observer VMs." Komprise also doesn't uses Stub files, which is a poor implementation adopted by the competitor for file access. We had a lot of issues in the past with stub files. Komprise has implemented 'bread crumbs', which are CIFS symlinks to the files on the Observer. It is a very good implementation and it works really well.
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.
