Message from discussion
DBMS_STATS cannot analyze clusters
Path: g2news2.google.com!postnews.google.com!t16g2000vbi.googlegroups.com!not-for-mail
From: John Hurley <hurleyjo...@yahoo.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: DBMS_STATS cannot analyze clusters
Date: Fri, 8 Apr 2011 06:50:14 -0700 (PDT)
Organization: http://groups.google.com
Lines: 24
Message-ID: <0e6b96e4-d2b2-472b-bff7-9a44d41a4780@t16g2000vbi.googlegroups.com>
References: <pan.2011.04.07.15.54.55@email.here.invalid>
NNTP-Posting-Host: 76.253.142.80
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1302270614 30460 127.0.0.1 (8 Apr 2011 13:50:14 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Fri, 8 Apr 2011 13:50:14 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: t16g2000vbi.googlegroups.com; posting-host=76.253.142.80; posting-account=_6ry2goAAAB8CmCVzS5u_8_rocyBncPn
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.16)
Gecko/20110319 Firefox/3.6.16,gzip(gfe)
Mladen:
# I have 3 tables which are always queried together and joined on the
same key. The common wisdom tells me that an index cluster is adequate
for such situation. The performance of the application did improve as
a result. The problem is with analyzing the cluster. DBMS_STATS cannot
do that:
I think the phrase "common wisdom" involving creating a cluster is
stretching it a bit. I have been around the block quite a while and
believe me clusters are pretty uncommon. Some authors talk about
using them and do recommend them for certain situations but in the
universe of people designing custom systems ... not often considered
AFAIK.
There is a whole set of history involving stats on clusters that for
the most part I am only vaguely aware of. It is probably release
dependent how well dbms_stats works with clusters and may also have
some issues with stats in parallel?
Do you have any monitoring in place that looks for objects that have
old statistics? Depending on the philosophy that you have in place
for when and if stats are gathered ( or not ) some tweaks to the
monitoring and exception reporting process could be looked at.