Re: Full tablescans on long tables

I don't know if there's a utility, but you can determine the tablespace(s) in question by looking at the end of the report for which tablespaces have a higher number of blocks read than physical reads. That would indicate the use of multiblock reads and therefore table scans.

In article <99vl2d$a23$1_at_kermit.esat.net>, Keith Jamieson <Keith.Jamieson_at_phoenix.ie> writes:
>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
>
>
>
>

• Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web ----- http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups NewsOne.Net prohibits users from posting spam. If this or other posts made through NewsOne.Net violate posting guidelines, email abuse_at_newsone.net