Re: Low hit ratio, but only for indexes

Actually it was the v$librarycache view, but never mind.

We are running SIEBEL.

I have been advised that it's probably because the queries aren't using indexes, which is what I suspected. I ran an explain plan on one of their slow queries and it does 2 full table scans of a 7M row table. Unfortunately they can't use hints (SIEBEL doesn't let them, something about platform independence), and the query has a '<>' in it, which I beleive won't use indexes.

nsouto_at_optushome.com.au.nospam (Nuno Souto) wrote in message news:<3c42c92c.1472055_at_news-vip.optusnet.com.au>...
> Andy doodled thusly:
>
> >As you can see, all the values are great, apart from the INDEX figure
> >which is terrible! Why is this, and how can I improve it?
> >
>
> I don't think the INDEX line means much on that one. never found a
> good explanation of why it never looks good. but it doesn't seem to
> matter much, so ignore it.
>
> >The SHARED_POOL_SIZE is set to 600MB.
> >
>
> yaba-daba-doo, attaboy! what you running there? SAP?
>
>
> Cheers
> Nuno Souto
> nsouto_at_optushome.com.au.nospam
Received on Mon Jan 14 2002 - 15:54:30 CST