Leroy, If you could include row source cardinality information it will help to identify areas for improvement using the throw-away methodology. From my perspective, it is also hard to read the output and understand the order of execution. Using the indentation method found in oracle doc (or including all the STAT lines as they are output) would be helpful. Don't give up hope, we're happy to help, we just need to have the information to assist. Regards, Daniel Fink Leroy Kemnitz wrote: > Here is the plan: > > SELECT STATEMENT Cost = 3414 > SORT ORDER BY > SORT GROUP BY > VIEW > WINDOW BUFFER > SORT GROUP BY > FILTER > TABLE ACCESS BY INDEX ROWID STUDENT_ANALYTICAL_BASE > NESTED LOOPS > VIEW > SORT GROUP BY > FILTER > TABLE ACCESS BY INDEX ROWID STUDENT_ANALYTICAL_BASE > NESTED LOOPS > TABLE ACCESS BY INDEX ROWID STUDENT_ANALYTICAL_BASE > INDEX RANGE SCAN PK_STUDENT_ANALYTICAL > INDEX RANGE SCAN PK_STUDENT_ANALYTICAL > FILTER > TABLE ACCESS FULL DUAL > FILTER > TABLE ACCESS FULL DUAL > FILTER > TABLE ACCESS FULL DUAL > FILTER > TABLE ACCESS FULL DUAL > FILTER > TABLE ACCESS FULL DUAL > FILTER > TABLE ACCESS FULL DUAL > FILTER > TABLE ACCESS FULL DUAL > FILTER > TABLE ACCESS FULL DUAL > INDEX RANGE SCAN PK_STUDENT_ANALYTICAL > FILTER > TABLE ACCESS FULL DUAL ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------