Daniel Roy wrote:
> 1) If you have lots of time and complete ownership of the database,
> shutdown and restart the database between queries.
> 2) Otherwise, issue "alter system flush shared_pool" between each
> query (only if there's no one else using the database please).
>
The only way to flush cash it to take the relevent tablespaces offline,
then put them back online. But, as I said before, what is the point?
You will not get any useful metrics from doing this.
> If I were you, I'd instead run each query twice, and keep the stats
> from the second run only. That way, you would only time the soft
> parse, not the hard one and the physical i/o. To answer your question,
> there's no way to tell Oracle to bypass the cache.
>
Better. I would recommend three or four runs after the first and
average the results.
--
AjA
Received on Wed Feb 26 2003 - 15:14:24 CST
