Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.tools -> Re: Unnecessary table scans

Re: Unnecessary table scans

From: Daniel A. Morgan <dmorgan_at_exesolutions.com>
Date: Tue, 03 Apr 2001 14:46:41 -0700
Message-ID: <3ACA44C1.7BEDC459@exesolutions.com>

> Has anyone come across this before and is it a known problem or a
> configuration issue ? We are running a datamart on 8.1.6 on AIX. All our
> fact tables have a composite primary key and bitmap indexes on the indidual
> columns of the primary keys. Statistics are adequate and up-to-date.
> A lot of our queries are however defaulting to a full table scan which is
> leading to long query times.
>
> An example of of timings would be
>
> A - Run query with no hints
> Time to run - 6 mins +
> Cost - 13736
>
> B - Run query forcing it to use composite index.
> Time to run - 1 min +
> Cost - 35558
>
> C - Run query forcing it to use bitmap indexes.
> Time to run - 10 secs
> Cost - 15478

What do you WHERE clauses look like? Give us an example from the above.

Daniel A. Morgan Received on Tue Apr 03 2001 - 16:46:41 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US