Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Analyzing procedures difference?

Re: Analyzing procedures difference?

From: <jmvegalerin_at_my-deja.com>
Date: Thu, 12 Aug 1999 07:02:28 GMT
Message-ID: <7otri0$j26$1@nnrp1.deja.com>


In article <7or6lv$dq$1_at_news.netway.at>,   "Oleg Roshchin" <oleg_at_ca-ib.com> wrote:
> Hi, all!
>
> What is the difference between

DBMS_Utility.Analyze_Schema
> and DBMS_Utility.Analyze_Part_Object?
> In the book "Oracle8 Server Tuning" it's written
to use the second
> procedure and nothing about the first one.
> Is the first procedure enough for analyzing
everything in the
> schema (to improve performance) or not?
>
> Oracle 8.0.5.
>
> Thanks in advance,
> Oleg,
> Moscow,
> Russia
>
>

analyze_schema(

                 schema varchar2,
                 method varchar2,
                 estimate_rows number
               default null,
                 estimate_percent number
                               default  null)
This procedure is equivalent to calling analyze_object on all

objects in the given schema.
analyze_part_object(
                 schema in varchar2 default
               null,
                 object_name in varchar2
                         default null,
                 object_type in char default
               'T',
                 command_type in char
                         default 'E',
                 command_opt in varchar2
                         default null,
                 sample_clause in varchar2
                              default
               'sample 5 percent')

for each partition of the object, run in parallel using job queues.
This procedure submits a job for each partition; you can control
the number of concurrent jobs with the
initialization parameter
JOB_QUEUE_PROCESSES. Object_type must be T (table) or I (index). Command_type can
be:

For V, command_opt can be 'CASCADE' when object_type is
T. For C or E, command_opt can be FOR table, FOR all
LOCAL indexes, FOR all columns or a combination of some of
the 'for' options of analyze statistics (table).

Sample_clause specifies the sample clause to use when
command_type is E.

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Thu Aug 12 1999 - 02:02:28 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US