Session ID: 171
Is sometimes difficult to quickly identify the root cause of a performance issue in the database. Automatic workload Repository (AWR) contains most of the information needed to identify these issues, but it could be overwhelming due the amount of data and statistics. Then, there's a need of a method to quickly identify if the database system is CPU or I/O bound along with the top SQL statements in that period of time.
This quick tip session will explain how to identify the time consumed and the time waited by the database. It also drills down to particular SQL statements responsible of this time consumed.
Objective 1: - How time is measured in the database
- Difference between time consumed and time waited
Objective 2: - Identify TOP SQL responsible of performance degradation
Objective 3: - Identify TOP segments having performance issues