I should have used different word(s). Sorry for causing concern. We did not observe any technical difference/flaws. But we have lots of log files (mostly insert only) which we donot want to be analyzed. We could get around this by dynamically generating script to use gather_table_statistics for desired tables. Gather_schema_statistics did not fit within our timeframe. Also one dubious behaviour i observed was (though i cannot reproduce it now) , the gather schema stats goes analyzing in alphabetical sequence and we had a big table which was getting hits almost all the time and the last analyzed time was updated in the user_tables for all tables between A - S while this C table was still not showing analyzed. I did not check the indexes of this C table at that time. HTH GovindanK On Thu, 25 Aug 2005 19:44:03 +0100, "Jared Still" <jkstill@xxxxxxxxx> said: > What kind of issues did you see with gather_schema_stats that could be > rectified by using gather_table_stats? > > > -- > Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist > > On 8/24/05, GovindanK <gkatteri@xxxxxxxxxxx> wrote: > > > > We had issues with gather_schema_stats and we moved over to > > gather_table_states and since then have peace of mind(9.2.0.6< > > http://9.2.0.6>); I have an build script that we are using in > > production which i will mail you offline later today. > > > > HTH GovindanK -- //www.freelists.org/webpage/oracle-l