It looks like you're new here. If you want to get involved, click one of these buttons!
I'd like to learn more about using EM on a dozen or so instances; Now that I'm trying to find referneces, they seem to be hiding. Thanks in advance.
We have configured OEM for many platforms including RDS. The only flags we would raise are the lack of DB Alert Log access and memory usage. AWS shapes are generally memory-poor in our opinion. We would recommend testing first to ensure that you are aware of the memory utilization of your specific OEM deployment. You can tune from there.
Thank you, Dan, it's appreciated.
we are also users of AWS RDS Oracle and OEM. the installation of the OEM Agent is done through the Option Group in AWS RDS.
the latest supported version of the OEM Agent is 13.4 which means you can run the OMS and OMR in version 13.4 with latest RU.
you need to setup your firewalls (security groups) to allow traffic in both direction from the RDS Oracle instance to the OMS and from the OMS to the OEM Agents running on AWS RDS.
we have been using this for about 18 months now, and recently we upgraded to OEM 13.4 and it works very well for performance monitoring, some of the actions will not work in the OEM console, because AWS RDS Service does not allow you to use the SYS users.
They have setup specific stored procedures for doing the same things as you would do with the SYS user, but the OEM platform is not "smart enough" to use the stored procedure, so it will fail many of the actions.
We would like to bring this topic to the Enterprise Manager Product Team as a feature enhancement, if there is enough interest in the community to push for this.
I believe there is a substantial benefit to using EM CC to operate RDS Oracle, and would be willing to push our account representatives in this direction if we find other companies to also request the same