Re: redo records

Hi,

I don't have a reference handy, but as I recall, when a commit is issued the transaction is marked with a commit record. The non-existence of this record is sufficient for Oracle to know it should be rolled back.

Hth,

Steve

In article <9612sg$25r$1_at_nnrp1.deja.com>,   letokai_at_my-deja.com wrote:
> In :
>
> Oracle8i Administrator's Guide
> Release 8.1.5
> 6 Managing the Online Redo Log
> chapter : Online Redo Log Contents
>
> I've read this :
> "...Redo records can also be written to an online redo log file
> before the corresponding transaction is committed. If the redo log
> buffer fills, or another transaction commits, LGWR flushes all
> of the redo log entries in the redo log buffer to an online
 redo log
> file, even though some redo records may not be committed. If
> necessary, Oracle can roll back these changes."
>
> If a rollback occurs how does Oracle do to process it?
> I mean it must have stored somewhere the information that a
> modification has not been commited yet.
> Where is stored this information?
>
> Sent via Deja.com
> http://www.deja.com/
>

Sent via Deja.com
http://www.deja.com/ Received on Fri Feb 09 2001 - 11:02:31 CST