"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in
news:_zaI9.91867$g9.256355_at_newsfeeds.bigpond.com:
>>
>> You can commit at whatever rate your heart desires, just keep in mind
>> that whenever you do this you increase risk of 1555 for some other
>> long running query against the same table.
>
> One more time, then. Commiting, in and of itself, does *not* increase
> the risk of 1555.
>
> Witness 9i, where the right to over-write rollback is completely and
> formally divorced from the commit, thanks to undo_retention. In
> earlier versions, sure -a commit meant you were free to over-write.
> But even in those versions, it didn't mean you *had* to over-write.
>
> Only the size of the rollback segment (or the lack of it) means that.
Yes, but consider the following scenario.
Assume I need to UPDATE a million records in a single table.
Assume that the RBS is large enough to handle all 1,000,000 records.
If only 1 COMMIT is issued at the very end, Oracle GUARENTEES that
no ORA-01555 error gets generated. If a COMMIT is issued every 1,000
records, getting an ORA-01555 is possible and there is NOTHING you can
to 100% ensure that an ORA-01555 won't occur.
Received on Sat Dec 07 2002 - 15:15:03 CST
