> To get the 10053 trace, you will need to reparse the query - you might have > to flush the shared pool or perform other shared sql invalidations (such as
I normally just modify the query to have comment /* test1 */ or /* test2 */ etc. in it. That way it's easy to search from possibly long 10053 trace for specific instances of your query. As Wolfgang stated, if you got only the QUERY string and query text in your trace then you're using either RBO, or your query isn't hard parsed which generates the full trace. If your statistics seem to be correct and optimizer mode is other than RULE and you still don't get the trace, try some hint such is first_rows, in your query to force CBO use. (of course this first_rows hint might change your execution plan itself, but is useful to test whether you get full 10053 trace at all). Tanel. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tanel Poder INET: [EMAIL PROTECTED] 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: [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).
