The rbs does not shrink to optimal when the transaction commits. The 2nd
transaction to 'find' that the rbs has extended beyond optimal will
cause the rbs to shrink.
--
Daniel W. Fink
http://www.optimaldba.com
Thomas Day wrote:
>With optimal, the rollback segment shrinks back to its optimal size as soon
>as the update, insert, or delete transaction is committed. However, there
>may be a long running query that is using that rollback segment for a
>consistent view of the database. If the rollback segment shrinks, the
>query cannot find the data that it needs. This results in a snapshot too
>old error.
>
>
>
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Daniel W. Fink
INET: optimaldba_at_yahoo.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Thu Jun 05 2003 - 10:50:00 CDT
