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: Performance impact of "MONITORING USAGE"

Re: Performance impact of "MONITORING USAGE"

From: Wolfgang Breitling <John.Doe_at_aol.com>
Date: Wed, 03 Dec 2003 02:01:38 GMT
Message-ID: <Xns9445C188AF60Cbreitliwcentrexcccom@198.161.157.145>


"Howard J. Rogers" <hjr_at_dizwell.com> wrote in news:3fcce7c4$0$20308$afc38c87_at_news.optusnet.com.au:

>
> "Howard J. Rogers" <hjr_at_dizwell.com> wrote in message
> news:3fcce40c$0$20308$afc38c87_at_news.optusnet.com.au...
>

>>
>> The overhead of setting segment_statistics to ALL is quite high, but
>> for TYPICAL, it's barely noticeable. And you can set and forget it.
>>

>
> Ooops. The init.ora parameter is called statistics_level. It's the
> view that's called v$segment_statistics. I got it right first time,
> but then went uncharacteristically loopy.
>

BTW. statistics_level = typical is the default:

SQL> exec print_table('select * from v$parameter where name like ''stat%''');

NUM                           : 769
NAME                          : statistics_level
TYPE                          : 2
VALUE                         : TYPICAL
ISDEFAULT                     : TRUE
ISSES_MODIFIABLE              : TRUE
ISSYS_MODIFIABLE              : IMMEDIATE
ISMODIFIED                    : FALSE
ISADJUSTED                    : FALSE
DESCRIPTION                   : statistics level
UPDATE_COMMENT                :

so no you get it automatically unless you change it. Received on Tue Dec 02 2003 - 20:01:38 CST

Original text of this message

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