SQL with High Concurrency Wait
 Concept

SQL Stats shows limits in collecting accurate timing for concurrency wait time, which leads to situations where high elapsed time is not accountable by subcomponents. We need to cross check SQL Stats using other techniques such as wait events in ASH, SQL trace, etc.

 Case Study Summary

The case scenarios summary:

 SQL statement with high elapsed time due to latch contention on buffer cache
 SQL statement with high elapsed time due to latch contention on library cache
Copyright 2011 Actrace. All Rights Reserved.
Home | Product | Case Study | Support | Download | Contact Us