> That gives you only the current use of sort segments. The same applies > to reasoning based on v$sort_usage and V$TEMP_SPACE_HEADER. The only > True Way(TM) of tuning sorts is by using v$sysstat and v$sesstat values,
I think tuning sorts based on "in-memory sort" vs "not-in memory sort" calculations might be ok in simple OLTP envivronments, but in modern DW and OLAP world they give too simplistic overiew of what's happening in database. I'd definitely add events 10032 and 10033 trace for tuning big sorts (v$tempstat and even 10046 trace with waits can be somewhat useful as well). 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).
