Hi Govind,
Just a thought: The value of _small_table_threshold - which is currently 2%
of the DB_BLOCK_BUFFERS. Any table undergoing FTS will be placed at the MRU
end rather than the LRU end and would thus live longer (and either cause
problems or alleviate it as the case may be!). Keep this in m
Title: RE: How to identify full table scans?
This
helps to identify the queries that could be tuned for LIO and/or PIO from a
SQL Tuning perspective. We can give this list to the development or
application teams so that they could independently work off this list
(hopefully
Title: RE: How to identify full table scans?
Govind,
Just curious why you are attacking the full table scans. I implemented something like this in the past utilizing Steve Adams' script expensive_sql.sql. It was very telling and very very useful.
Lisa Koivu
Oracle Dat
