RE: Monitor contention

The kind that negatively affects user's response time.

10G? ...have a look at ASH to see what actions consume response time. Isolate the most important business actions that utilize the RAC environment in question. Identify the database actions that correlate to the business actions. Identity satisfactory response time limits for those database actions. Monitor those database actions against those limits. When those limits are exceeded perform extended trace on a session performing the actions that take longer that agreed upon acceptable lengths of time. Have a look at the trace file and see where the time is spent. Reduce that time.

chris

-----Original Message-----
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

CONFIDENTIALITY NOTICE:
        This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email reply.

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