Re: Full tablescans on long tables

First point is that the '5 blocks is large' thing is Oracle version 6. A smal table is (by default) a table that is less than 2% of the db_block_buffer size.

One easy option to find out where the problem is to look at v$SQL for queries where disk_reads is reasonably large and close to buffer_gets. (e.g.

    where disk_reads > 100
    and buffer_gets < 2 * disk_reads
)

It isn't perfect, but it's usually a good starting point

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

Practical Oracle 8i:  Building Efficient Databases
Publishers:  Addison-Wesley

Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html



Keith Jamieson wrote in message <99vl2d$a23$1_at_kermit.esat.net>...


>After running utlbstat.sql and utlestat.sql, I get a lot of full table

 scans


>on long tables(ie more than 5 data blocks).

>

>Is there any utility, view etc which will let me see what the names of

 these


>long tables being accessed are.

>

>Essentially, I want to see if its one or two particular tables which are

>being hit frequently, or whether I have a problem in General.

>

>TIA.

>

>Keith Jamieson

>

>

>

>