Re: Roll forward using Archive Logs

Luis Santos schrieb:
> A pending transaction should not be rollforwared. A pending transaction
> during a database crash becomes a lost, uncommited transaction.
>

This is from the Database Concepts:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/glossary.htm#i997675 <quote>
cache recovery

The part of instance recovery where Oracle applies all committed and uncommitted changes in the redo log files to the affected data blocks. Also known as the rolling forward phase of instance recovery. </quote>
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#sthref2387 <quote>
The first step of recovery from an instance or disk failure is called cache recovery or rolling forward, and involves reapplying all of the changes recorded in the redo log to the datafiles. Because rollback data is also recorded in the redo log, rolling forward also regenerates the corresponding rollback segments

Rolling forward proceeds through as many redo log files as necessary to bring the database forward in time. Rolling forward usually includes online redo log files (instance recovery or media recovery) and could include archived redo log files (media recovery only).

After rolling forward, the data blocks contain all committed changes. They could also contain uncommitted changes that were either saved to the datafiles before the failure, or were recorded in the redo log and introduced during cache recovery.
</quote>

Do you have certain reasons to think that particular documentation is wrong ?
Best regards

Maxim Received on Thu May 18 2006 - 05:10:16 CDT