Re: rollback segment too old

From: Richard Foote <richard.foote_at_bigpond.com>
Date: Fri, 21 Jun 2002 21:35:33 +1000
Message-ID: <N9EQ8.17106$Hj3.56570@newsfeeds.bigpond.com>

Hi Pinto,

Probably not. This parameter (along with TRANSACTIONS) is only used to determine how many rollback segments to have online at startup. Generally used to automate the number of public rollback segments will use.

As suggested by another poster, create a few extra rollback segments and put them online.

Also, consider running the job that gets the snapshot too old error at a less "busy" time.

Regards

Richard

"Pinto" <ucanmailme_at_india.com> wrote in message news:aev0oe$f3b$1_at_news.mch.sbs.de...
> will it help if i increase the transactions_per_rollback_segment value.
> currently it is the default value of 5.
> Thanks,
> Pinto.
>
> "Knut Talman" <knut.talman_at_mytoys.de> wrote in message
> news:3D130468.826B5A8A_at_mytoys.de...
> > Pinto wrote:
> >
> > > if you can see, the wraps have more than doubled. and as expected i am
> still
> > > getting ora-1555
> >
> > Not only the size of a rollback segment can become a bottleneck also the
> number
> > of rbs is important. Every transaction has to use the header of the rbs
to
> enter
> > its information. If there are no slots left (in the header) you'll get
> > ORA-01555, even if there are a lot of free rollback segment blocks.
> >
> > Regards,
> >
> > Knut
>
>
Received on Fri Jun 21 2002 - 06:35:33 CDT