RE: optimizer_max_permutations

turns out the parameter only governs how much time the optimizer can spend looking for the best execution plan... 80000 means no limit, OK for small SQL queries but for complex ones parsing can take too long.

So this has nothing to do with TEMP space usage after all. sort_area_size is probably the one for TEMP.

Patrice.

-----Original Message-----
Sent: Tuesday, August 26, 2003 11:58 AM
To: ORACLE-L_at_fatcity.com
Cc: BoivinP_at_mar.dfo-mpo.gc.ca

Yes, it is required in one of our COTS applications.

Inserts into complex views with instead-f triggers.

The views are quite complex, ridiculously so, one might say.

Before setting optimizer_max_permutations=1000, it took a very long time to parse those views.

Jared

On Tue, 2003-08-26 at 05:44, Boivin, Patrice J wrote:
> Has anyone worked with this one?
>
>

http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76961/ch11
> 23.htm#81357
>

<http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76961/ch1
> 123.htm#81357>
>
> Patrice.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Boivin, Patrice J
  INET: BoivinP_at_mar.dfo-mpo.gc.ca

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).