After collecting stats, I export them to a user table. Then I can analyze a whole bunch of things like which segments allocate blocks at what frequency etc. Raj On 7/26/05, Johnson, George <GJohnson@xxxxxxx> wrote: > > > We are currently using the traditional analyze command for both > tables and indexes once a week. I have the job of converting our shell > script based analyze scripts to in DB pl\sql based mechanisms. > > On the subject of statistics collection, we currently seem to spend > and inordinate amount of time collecting all sorts of obscure statistics > about tables and indexes, I would like to simplify this to keep a more > simple set of statistics, to determine our growth patterns. The dbms_stats > package doesn't seem to support options like the use of the old > index_stats > table, so I was wondering what other people were doing in terms of stats > collection for monitoring growth patterns, when using dbms_stats. > > Any thoughts you could share, would be most welcome > > Rgds > > > > **************************************************************************** > This message contains confidential information and is intended only > for the individual or entity named. If you are not the named addressee > you should not disseminate, distribute or copy this e-mail. > Please notify the sender immediately by e-mail if you have received > this e-mail by mistake and delete this e-mail from your system. > E-mail transmission cannot be guaranteed to be secure or error-free > as information could be intercepted, corrupted, lost, destroyed, arrive > late or incomplete, or contain viruses. The sender therefore does not > accept liability for any errors or omissions in the contents of this > message which arise as a result of e-mail transmission. > If verification is required please request a hard-copy version. > This message is provided for informational purposes and should not > be construed as an invitation or offer to buy or sell any securities or > related financial instruments. > GAM operates in many jurisdictions and is > regulated or licensed in those jurisdictions as required. > > **************************************************************************** > > -- > //www.freelists.org/webpage/oracle-l > -- ------------------------------ select standard_disclaimer from company_requirements where category = 'MANDATORY';