There's something I don't understand.  Why use the wait interface to investigate "db file scattered read" or "db file sequential read"?
 
The end result is finding an SQL statement that does a lot of reads.  There's no guarantee it's a poorly tuned SQL statement, just that it does a lot of reads.
 
If that's what you want, why not just query v$sql and order by physical reads?  Doing this is a whole lot easier.  Also, unlike the hit and miss results from v$session_wait, v$sql provides a comprehensive picture.
 
Thanks for your input.  Cheers!
 

Reply via email to