Is this considered RBS extending June 10, 2004 - am UTC the rbs manages storage. If a TX requests "n blocks" and the current extent in the RBS cannot satisfy this then the RBS will either a) go to the next extent in the "ring" if the next extent in the rbs ring contains no active transactions.b) allocate a new extent (if possible, return failure or suspend the transaction otherwise) and insert it into the rbs ring at this point.
On your system however the rollback wraps every 2 minutes due to lots of little transactions going on. What you need to do here is size rollback so that it wraps less frequently (less frequently then your long running queries). I think when RBS wraps to extent 1., it starts over writing and hence the chance for 1555 Am I correct if I say, as long as any of the Rollback segments do not wrap to extent 1, there will not be a 1555 even during commit in the for loop sql queries.
Here if I sized the rollback so that I had 10, 10meg segments (not so they could GROW to 10meg but that they are starting at 10meg) we would wrap maybe every 20minutes now. Therefore, if all the RBS are very large with no wraps during a query, 1555 is mute Thanks Therefore does the circle is established by min extents.
if you are in extent N and N 1 is being used still (or with AUM N 1 contains information that cannot yet be overwritten because of the undo_retention), we'll allocate a new extent and stick it in there.
I still am a bit unclear what makes the RBS advance.
if you size your rollback adequately, neither will you.
The ORA-1555 happens when people try to save space typically.
That user is updating\inserting\deleting a lot of database records without committing.
Oracle clears out any unneeded transactions in the rollback segment but eventually it fills up and the error occurs. User B logs into the data base and is updating\inserting\deleting a lot of database records, but is committing every 100 records.
I like have a good understanding of TX extending vs.