Gorman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 28, 2002 6:43 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Parallel degrees in DBMS_STATS
>
>
> I'd be interested to know of the bugs you've found on
> DBMS_STATS; most of
> the bugs I've
I'd be interested to know of the bugs you've found on DBMS_STATS; most of
the bugs I've seen logged against it were created due to differences with
ANALYZE, and in the end it was determined that ANALYZE produced the wrong
result, not DBMS_STATS...
Anyway, the symptoms you describe match those fo
onal, Sussex, WI USA
> -Original Message-
> From: Mohammad Rafiq [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 28, 2002 3:01 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Re: Parallel degrees in DBMS_STATS
>
>
> Run following query and check whether rel
Run following query and check whether relevent table/index has degree > 1
select index_name,degree from dba_indexes where degree > 1
/
select table_name,degree from dba_tables where degree > 1
/
If degree > 1 then it will use nymber of PQ process equivalent to number od
degree
Regards
Rafiq
Hey all,
I'm using DBMS_STATS (despite it's bugs) on 8.1.7.2.0 / HPUX 11.0. When I
specify "degree => 2" in the parms for either GATHER_SCHEMA_STATS or
GATHER_TABLE_STATS, I notice that 4 "p" processes are kicked off (e.g.
"ora_p001_sid"). Since this is on a test system, there is only one
proce
