John: That makes perfect sense in view of the fact that only the /*+ RULE */ hint makes the query run. I'm not gonna try and find the root cause any more; I've modified my queries and I get answers again.
My Thanks to all who have helped me with this issue. Cheers, Mike -----Original Message----- Sent: Tuesday, August 20, 2002 1:24 PM To: Multiple recipients of list ORACLE-L Mike, > Ok...this is strange. The optimizer_mode is set to RULE, but if > I put a RULE hint into the SQL it runs OK. I tried increasing This is almost clearly a case of the CBO being forced for whatever reason. And there are many :( Cut and paste from the Fine Manual (Oracle 8i Designing and Tuning for Performance). See the last 'Note:' :) The Optimizer 4-19 Features that Require the CBO The use of any of the following features requires the use of the CBO: n Partitioned tables n Index-organized tables n Reverse key indexes n Function-based indexes n SAMPLE clauses in a SELECT statement n Parallel execution and parallel DML n Star transformations n Star joins n Extensible optimizer n Query rewrite (materialized views) n Progress meter n Hash joins n Bitmap indexes n Partition views (release 7.3) Note: Even if the parameter OPTIMIZER_MODE is set to RULE, the use of these features enables the CBO. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Vergara, Michael (TEM) 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).
