Denodo is the eponymous data integration platform from the global company headquartered in Silicon Valley.
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.
Denodo allows us to create and combine new views to create a virtual repository and APIs without a single line of code. It is excellent because it can present connectors with a view format for downstream consumers by flattening a JSON file. Reading or connecting to various sources and displaying a tabular view is an excellent feature. The product's technical data catalog is well-organized.
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.
Caching - but I am sure it will be improved by now. There were times when we expected the cache to be refreshed but it was stale.
Schema generation of endpoints from API response was sometimes incomplete as not all API calls returned all the fields. Will be good to have an ability to load the schema itself (XSD/JSON/Soap XML etc).
Denodo exposed web services were in preliminary stage when we used; I'm sure it will be improved by now.
Export/Import deployment, while it was helpful, there were unexpected issues without any errors during deployment. Issues were only identified during testing. Some views were not created properly and did not work. If it was working in the environment from where it was exported from, it should work in the environment where it is imported.
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.
Denodo is a tool to rapidly mash data sources together and create meaningful datasets. It does have its downfalls though. When you create larger, more complex datasets, you will most likely need to cache your datasets, regardless of how proper your joins are set up. Since DV takes data from multiple environments, you are taxing the corporate network, so you need to be conscious of how much data you are sending through the network and truly understand how and when to join datasets due to this.
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.
