Imagine being able to prove to yourself and others a performance problem is not a database issue. There are a few ways to infer the problem resides elsewhere, but it’s difficult for people to believe you. However, by creatively using ASH data we can prove the problem does not reside in the database.
For example, suppose a batch process is “taking too long” yet you can not find evidence of the process in an AWR report, analyzing AWR data or even standard ASH analysis.
The combination of enabling ASH to temporarily collect “non active” sessions, step-by-step watching an Oracle session while paying close attention to the “SQL*Net message from client” event, we can prove a performance issue resides outside of the database!
In this presentation, I will demonstrate exactly how to do this. I’ll start with a quick ASH introduction, then dive into Oracle’s time model, what to look for and how to look for it and finally how to interpret the results.
Join me as I show you how to prove the database is not the problem!