RE: Growth pattern statistics collection after analyzing
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: <GJohnson@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 26 Jul 2005 09:05:50 -0700
For monitoring growth patterns, you can just query dba_segments or dba_tables
and dba_indexes (after a regular analyze/dbms_stats.gather_*_stats), depending
on exactly what you want to monitor - segment size, used/free space, HWM, etc.
Index_stats (populated by analyze . . . validate structure, which requires an
exclusive lock) is typically only needed if you want to check for index
sparseness, selectivity, density, the infamous out-of-balance myth, etc. In my
experience, these things are only needed occasionally for troubleshooting
performance problems, or if you're bored and just want to rebuild some indexes
to make it look like you're busy :-)
I usually just run dbms_stats.gather_schema_stats, with either compute, or
estimate as appropriate for your environment, and cascade=>true. Don't bother
creating histograms (larger than the default of 1 bucket) unless justified by
some specific problem, such as a query using a poor execution plan due to
inaccurate estimation of the cardinality because of skewed data distribution.
Regards,
Brandon
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Johnson, George
Sent: Tuesday, July 26, 2005 6:43 AM
To: 'oracle-l@xxxxxxxxxxxxx'
Subject: Growth pattern statistics collection after analyzing
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
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
