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 the sort_area_size, but no joy. The segment with the largest number of extents is the silly TEMP segment with 985. After that is IDL_UB1$ with 739, and it tapers off quickly after that. On the other hand, this query runs fine on our SAP system, and it has thousands of tables and lots of extents.
Well, the RULE hint in a RULE system seems to have worked. Weird. I never woulda tried that. Thanks, Mike -----Original Message----- [mailto:[EMAIL PROTECTED]] Sent: Monday, August 19, 2002 4:28 PM To: Multiple recipients of list ORACLE-L or is that 1 db set to first_rows? If so try the query with a rule hint? Bruce Reardon -- 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).
