Re: Uncommitted Data

From: HansF <News.Hans_at_telus.net>
Date: Thu, 16 Jun 2005 05:08:55 GMT
Message-Id: <pan.2005.06.16.05.11.57.513065@telus.net>

On Wed, 15 Jun 2005 23:06:23 -0400, VC interested us by writing:

>
> "HansF" <News.Hans_at_telus.net> wrote in message
> news:pan.2005.06.15.15.27.46.709477_at_telus.net...

>> On Wed, 15 Jun 2005 07:59:17 -0700, agarwalp interested us by writing:
>>

> [...]

>> That which is committed is in the tablespace data files.

>
> This is not correct. 'That which is committed' will be in the transaction
> log (redo log), but not 'in the tablespace data files'.
>

Correction accepted - I was incomplete in my statement. Until it's written to the log file, the commit is not considered complete. That does not imply write to the data tablespace. And until it's written to the data tablespace, the roll forward will occur during instance recovery.

Again, from the manual,

"
DBWn periodically writes buffers to advance the checkpoint, which is the position in the redo thread (log) from which instance recovery begins. This log position is determined by the oldest dirty buffer in the buffer cache.
"

-- 
Hans Forbrich                           
Canada-wide Oracle training and consulting
mailto: Fuzzy.GreyBeard_at_gmail.com   
*** I no longer assist with top-posted newsgroup queries ***

Received on Thu Jun 16 2005 - 00:08:55 CDT