Re: help

From: DA Morgan <damorgan_at_exesolutions.com>
Date: Mon, 10 Feb 2003 08:43:10 -0800
Message-ID: <3E47D69E.3DFCEA67_at_exesolutions.com>


Niall Litchfield wrote:

> "Richard Nield" <richard.nield_at_ntlworld.com> wrote in message
> news:ugx1a.1372$mH4.975_at_newsfep1-gui.server.ntli.net...
> > Thanks. Is this something our DBA should have made us aware of?
>
> I personally think that that is a tough call, DBMS_STATS is the currently
> recommended way of collecting optimiser stats, and certainly if you have
> large databases with high availability/performance requirements is likely
> the best way to go. It does have its downsides though, (like causing
> ORA-00600 errors for us in both 8.1.7 and 9.2). I do think that your DBA
> should have been aware of the package though and actively considered it.
>
> As far as Dan's comment about requiring DBMS_STATS in order to work with new
> features, I'm fairly sure that this is incorrect. You *do* require the CBO
> for some features - theres a list in the docs - but as far as I know analyze
> will compute stats for these as well. The big adavantages it seems to me are
> those that Sybrand listed.
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK

Never had an ORA-00600 from DBMS_STATS on HP/UX 11, Solaris 8, Win NT4, Win2K, or WinXP with either 8.1.7.3 or 9.2.0 so I would look elsewhere for the cause of any 600s.

I stand ready to be corrected but I believe only DBMS_STATS collects optimizer information for partitions and index organized tables. Though I do agree that Sybrand's list are the items of primary importance.

Daniel Morgan Received on Mon Feb 10 2003 - 17:43:10 CET

Original text of this message