| "db file scattered read" too high and Query going for full table scan-Why ? [message #166024] |
Tue, 04 April 2006 02:07  |
tayalarun
Messages: 20
Registered: December 2005
|
Junior Member |
|
|
Hi,
I had a big table of around 200mb and had a index on it.
In my query I am using the where clause which has to use the
index. I am neither using any not null condition
nor using any function on the index fields.
Still my query is not using the index.
It is going for full table scan.
Also the statspack report is showing the
"db file scattered read" too high.
Can any body help and suggest me why this is happenning.
Also tell me the possible solution for it.
Thanks
Arun Tayal
|
|
|
|
|
|
|
|
|
|
| Re: "db file scattered read" too high and Query going for full table scan-Why ? [message #166151 is a reply to message #166024] |
Tue, 04 April 2006 18:11  |
RaeMarvin
Messages: 7
Registered: April 2006
|
Junior Member |
|
|
To help could you post the stats details below.
Index: Index_name, blevel, leaf_blocks, distinct_keys, clustering_factor, avg_leaf_blocks_per_key, avg_datta_blocks_per_key.
Table: blocks, num_rows, freelists
column: column_name, density, num_nulls
The analyze command your using, the predicates at least from the query, version of Oracle as this has major impact on the plan and the explain plan.
From that information somone might be able to aid more.
But as stated don't be surprised if a FTS is the deemed as th best path.
Cheers
Rae
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
