That's how myths start. That was true for Oracle 8 and earlier. As of Oracle 9 you should be OK analyzing catalog tables. Oracle has by now strewn lots of /*+ rule */ hints in the recursive sql to eliminate/minimize the performance hits experienced before. I doubt that there is a need for it though (analyzing sys tables that is). Maybe if you have some homegrown scripts that join catalog tables/views in ways not foreseen by the developers or with other tables, statistics on the sys tables may help. At 12:41 PM 7/29/2004, you wrote: >Hi Larry >SYS schema don't need be analyzed, using tom kyte's word "it's magical" and >must not be analyzed >if you got statistics in sys, you can ruin it's performance. >sys schema don't have to be touched, this means don't create user tables in >sys, etc. > > > >Juan Carlos Reyes Pacheco >OCP Regards Wolfgang Breitling Centrex Consulting Corporation www.centrexcc.com ---------------------------------------------------------------- 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 -----------------------------------------------------------------