Please share with the community what you think needs improvement with Oracle Enterprise Manager.
What are its weaknesses? What would you like to see changed in a future version?
RMAN tools need improvement. There are some doubts about the Oracle policy on price quotes. I have a good relationship with the customers and If I start dealing with them, and get them a discount, then that discount is available to all of the Oracle partners. I prefer the way it works with other companies, like HP, where any discount that I negotiate on behalf of a customer will be available only to me.
With regards to masking still, some options could be added like running in simulation mode, creation of audit file option, file summary, file after masking.
They should improve the hover text context. This would provide assistance whenever a task is attempted by a DBA.
The product is pretty comprehensive, but quite resource hungry. This might be due to the majority of the application seemingly being written in Java. Also, better mobile access would be useful.
Oracle is always making improvements to Oracle Enterprise Manager. I think Enterprise cloud integration presents new management challenges.
Customization for double secure / nonce based / token based Business Transaction Management. Where you can monitor DB calls as well as Web service calls under firewall.
Reporting and statistical charting is largely still left up the end-user to develop custom solutions. Having more pre-built standard industry-generic reports using Business Intelligence (BI) Publisher provides out-of-the box basic analysis would be increasingly useful. The actual product inventory discovery and configuration process has improved, but is still fairly convoluted and requires multiple pre-requisite setup steps to be completed, requiring numerous Cancel, Go back and set something else up, then Return to the process you were performing types of process flows. It works really well if all the technology stack layers are current releases, but the more heterogeneous the architecture is, the more you will spend more time configuring outlying systems, or systems that aren't quite up-to-date. The OMC array of offerings is quite numerous, so when you first try to navigate the menu offerings, you'll experience 7 to 10 layers of click-throughs to find what you may be looking for in the mass number of options. There is currently a hybrid UI between the Cloud Classic menus and the revised OCI v2.0 menus that has many duplicates, but are found using different navigation paths, which can be confusing. While the main dashboards are fairly clear, there are often click-throughs that lead you down not so clear breadcrumb trails during your navigation.
Patching. It's extremely difficult to determine what requires patching and the process to patch each component is slightly different. In desperate need of a single patch or a simplified process at a minimum. OEM 13c is out and we have it installed. There seems to be some potential bugs associated with implementing third party certificates and the Tuning Advisor so just something to consider before upgrading. One new issue came up recently. We upgraded to 12.2 and went with a container/pdb model for each database. After doing so, some of the functionality gets a little tricky with OEM. For some things you need to be in the PDB to work and for other things you need to be in the cdb$root. You can create SQL Profiles through OEM but dropping them through OEM has become a point in futility. Instead, we are doing more manual SQL Tuning Advisor functional through sqlplus which works well.