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: Shrewd way to avoid 'snapshot too old'?

Re: Shrewd way to avoid 'snapshot too old'?

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: 2000/06/13
Message-ID: <960920049.22475.0.nnrp-13.9e984b29@news.demon.co.uk>#1/1

Only if there is a reason why the rollback segments cannot extend (max extents
reached, tablespace too small). The
presence of the uncommitted transaction
simply ensures that the rollbacks extend instead of wrapping.

Naturally you would have OPTIMAL set
so that after this special job had finished the rollbacks would eventually shrink.

--

Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Greg Stark wrote in message
<87d7lmffqi.fsf_at_HSE-Montreal-ppp138319.sympatico.ca>...

>
>
>Don't the transactions just get "Can't extend rollback segment" and fail
>themselves?
>
>--
>greg
Received on Tue Jun 13 2000 - 00:00:00 CDT

Original text of this message

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