Re: Monitoring Oracle RDS

From: Lei Zeng <leizeng2003_at_yahoo.com>
Date: Thu, 13 Dec 2012 14:19:58 -0800 (PST)
Message-ID: <1355437198.25735.YahooMailNeo_at_web140006.mail.bf1.yahoo.com>



Michael:
You can install OEM database control with your RDS instance. You need create Option group first and then choose it when you create your RDS instance. For existing RDS instance, you may not be able to do it and you can try.

http://aws.amazon.com/about-aws/whats-new/2012/05/29/amazon-rds-for-oracle-announces-oem-support/

I have Oracle diagnostic package license and my RDS instances have AWR and ASH data. I offer DBspeed to my customer as performance monitoring/tuning tool. DBspeed can display top SQL, top wait events, etc. My customers also use it to create AWR and ASH reports to view in the GUI embedded. You can try DBspeed free for one year and hope you like it.

DBspeed  http://dbspeed.com/index.html

There are some case studies on the website. If you are familiar with AWR and ASH reports, you know this tool.

Regards,
Lei



 From: Michael Wehrle <michaelw436_at_gmail.com> To: oracle-l <oracle-l_at_freelists.org> Sent: Thursday, December 13, 2012 7:55 AM Subject: Monitoring Oracle RDS  

All, I am working on migrating some oracle databases into Amazon RDS. Is there a good monitoring solution out there for these instances? The provided cloudwatch is minimal, and not useful at all in terms of performance metrics, wait events, top sql, top activity. OEM seems out of the question, since its an agent-based tool, and with RDS you give up access to the server where the db resides. Cloudwatch monitors the following for RDS:

CPU,Storage,Memory,Swap,Connection Count,I/O,Replag

I need to be able to see some more useful stuff. At this point, I only see that I may have to use statspack or something similar to it, but thats all manual work. A GUI for my db customers would be ideal.

Suggestions?

--

http://www.freelists.org/webpage/oracle-l
--

http://www.freelists.org/webpage/oracle-l Received on Thu Dec 13 2012 - 23:19:58 CET

Original text of this message