I found two bugs on Metalink dealing with this.  The first, 1890016, can be
ignored because the GATHER only fails if you specify an invalid granularity.
Well duh.  The second, bug 1192012, will only cause the first table in the
schema to be skipped.

In our case, the first table is first alphabetically (and perhaps the first
created in the schema), which happens to contain no rows.  So I still use
the GATHER_STALE option on 8.1.6.

HTH!  :)

Rich Jesse                           System/Database Administrator
[EMAIL PROTECTED]              Quad/Tech International, Sussex, WI USA

> -----Original Message-----
> From: Grabowy, Chris [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 16, 2002 10:44 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Dba_tab_modifications question
> 
> 
> Thanks Prakash.
> 
> I was poking around in Metalink and discovered it.  Luckily, 
> I'm on 9i, so I
> will be checking out this feature.
> 
> -----Original Message-----
> Sent: Thursday, May 16, 2002 11:24 AM
> To: Multiple recipients of list ORACLE-L
> 
> 
> Chris, I remember from Metalink that you cannot use the 'gather stale'
> option in dbms_stats.gather_schema_stats. There is a bug in 
> 8i and supposed
> to be fixed in 9i. So they still advise to run a job daily to 
> gather the
> correct statistics.
> 
> Thank you Gopalakrishnan, Kirti and John for clearing my doubt!
> 
> Prakash
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jesse, Rich
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to