Re: Caution on LOG_PARALLELISM
Good that it becomes a hidden parameter in 10g. The bug number that
was given to me was 4008013 but was not table to see the bug details.
On 8/10/05, Tanel P?der <tanel.poder.003@(protected):
> > Lesson I learnt from this exercise is that always use log_parallelism
> > with caution and would also suggest folks not to try this directly in
> > a critcal environment.
> We'll starting from 10g, log_parallelism becomes a hidden parameter and also
> there is such a thing like dynamic log parallelism, that Oracle can change
> the number of redolog strands on the fly. So from 10g you really can't
> control it, unless instructed so by support...
> Do you have the bug number?