RE: Monitor contention

Simple answer to this one: Anything that causes increase in business task response times.  

So, if you're monitoring end-user response times with sufficient drill-down data (such as you can get from your Oracle extended SQL trace data), you're monitoring what you need to monitor. If some kind of contention causes a performance problem, you'll be able to notice its presence in someone's response time. If some kind of contention does not negatively influence someone's response time, then it's not a performance problem-by definition.  

This is true whether you're running RAC or not, and whether you're using a SAN or not.    

Cary Millsap

Hotsos Enterprises, Ltd.

http://www.hotsos.com

Nullius in verba  

Hotsos Symposium 2008 / March 2-6 / Dallas

Visit www.hotsos.com for curriculum and schedule details...

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of BLock_at_dvfs.com Sent: Friday, May 11, 2007 12:43 PM
To: oracle-l_at_freelists.org
Subject: Monitor contention  

What kinds of contention do we still need to look for in a RAC and SAN environment?

Thanks

Brian Lock
DBA - East Campus

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