Please fix what i am missing here.
The argument against frequent commits is that oracle needs the
transaction details, which is wiped out by COMMIT, to supports its
multiversioning facility.
But i have read that when oracle goes to rollback segments for getting
the status of a trans id, and if the trans id not present it regards it
as COMMITTED. This belief is what raised my question. ??
If this not true, then what if a block update is committed->
transaction id of the block does not indicate the commit status. and
eventually after some time (read days) the rollback segments (which
contains the status of that transaction id) gets wiped out, Now if i
read that block will it give the 01555 error??
Received on Mon Jan 16 2006 - 09:25:28 CST
