PMFJI.
If you set OPTIMIZER_GOAL=FIRST_ROWS for the entire
database you'll have a *big* problem in your hands with
most of the dictionary views, including catexp, becoming
exceedingly slow.
It's better (if you can) to stay with CHOOSE and analyze
just what you need. Then you fiddle with OPTIMIZER_COST_ADJ
and OPTIMIZER_INDEX_CACHE to get the right balance of index
vs table scan.
Works for me. Except I had to stay with FIRST_ROWS like it
or not (due to a bug) and it hasn't been good for dict views
at all...
Cheers
Nuno Souto
[EMAIL PROTECTED]
http://www.users.bigpond.net.au/the_Den
----- Original Message -----
>
> I would have considered setting optimizer_goal=first_rows and would
> appreciate hearing your ideas on why you decided to set
> OPTIMIZER_INDEX_COST_ADJ to 30 instead. Thank you.
>
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Nuno Souto
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
