When we manage Oracle databases on the AWS platform, we find it somewhat cumbersome to monitor the database and servers in one place; whether that be Oracle OEM or AWS CloudWatch. This blog will give suggestions on how to use both OEM and CloudWatch to monitor your Oracle databases on AWS RDS.
While Oracle OEM monitors the specific database alerts such as alert log errors, failed jobs, tablespace usage etc., it does not monitor server specific issues such as CPU utilization, OS space issues and memory usage. CloudWatch can monitor those OS specific metrics.
Together, Oracle OEM and AWS CloudWatch can be configured to monitor the database environment without missing critical, possible failure/outage events.
Oracle OEM Monitoring
OEM monitoring should be set up using DBA and company standards for any other Oracle database.
This is an example of an OEM template used for monitoring a production database instance:
…and so on.
The metrics are quite comprehensive and monitor the database systems well.
Then AWS Cloud Watch is configured in addition to comprehensibly monitor the systems sending alerts as needed.
AWS CloudWatch Monitoring
Here are some examples of CloudWatch monitoring of an RDS server. As you can see, these metrics are inclusive of the entire RDS server, not just the database instance.
Below is an example of some of the metrics that can be quickly set up to monitor through AWS CloudWatch.
This first metric shows Average CPU Utilization, OS Storage Space, Database Connections and Memory metrics.
Swap space can also be easily monitored and reported.
This is an example of some of the throughput metrics.
Overall memory metrics…
As demonstrated, Oracle OEM monitoring and AWS RDS CloudWatch can be used in tandem to monitor your Oracle databases on the AWS RDS Cloud platform. Through both tools, email notifications can be configured to multiple email addresses or distribution lists to assist DBAs, OS Admins and AWS architects monitor the environments with confidence and transparency at the Oracle database level and the AWS RDS level. If you’re looking for assistance with your database monitoring needs, please contact us.
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.
Imagine over 100 logins on the source server, you need to migrate them to the destination server. Wouldn’t it be awesome if we could automate the process?