Re: bstat/estat table scans (long tables) breakdown?

A long table (since about 7.0.16) is a table that is more than 2% of the db_block_buffers value. The 5 blocks rule was pretty much out with Oracle 6.

Check v$sql for statements where buffer_gets < 2 * disk_reads and disk_reads > 2% of db_block_buffers - this will give you some clues.

Also examine v$filestat for files where blocks reads >> read requests - this may give you a hint about which tablespaces the guilty tables are in.

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Dan Bikle wrote in message <7l9ioi$ihn$1_at_samba.rahul.net>...
>I'm working with a file, report.txt, created by the scripts:
>$ORACLE_HOME/rdbms/admin/utlbstat.sql
>$ORACLE_HOME/rdbms/admin/utlestat.sql
>
>The file reports on a statistic:
>
>table scans (long tables)
>
>For example:
>
>table scans (long tables) 204
>
>which means the rdbms did 204 full table scans on long tables
>(tables larger than 5 blocks)
>
>Is it possible to get a breakdown on these 204 full table scans?
>
Received on Tue Jun 29 1999 - 15:40:49 CDT