Message-ID: <012601c86584$337c9430$0200a8c0@Primary>
From: "Jonathan Lewis" <jonathan@jlcomp.demon.co.uk>
To: <oracle-l@freelists.org>
References: <200802020817.m128HEmM020069@smtp43.singnet.com.sg> <6e9345580802020121y401aa5ebifecde9f3537896a3@mail.gmail.com>
Subject: Re: Usage of COMMIT NOWAIT, BATCH
Date: Sat, 2 Feb 2008 10:13:04 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed;	charset="iso-8859-1";	reply-type=original
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-to: jonathan@jlcomp.demon.co.uk


As much data as had not been protected by the log writer since
it last write - i.e. as much as three seconds of log.

Of course, if you had a long running transaction that took 
three hours to complete, and the COMMIT for that transaction
was in that three seconds, then the three hours would be rolled
back on recovery.


Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com

Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


----- Original Message ----- 
From: "LS Cheng" <exriscer@gmail.com>
To: <hkchital@singnet.com.sg>
Cc: <oracle-l@freelists.org>
Sent: Saturday, February 02, 2008 9:21 AM
Subject: Re: Usage of COMMIT NOWAIT, BATCH


> Hi
> 
> It just occured to me yesterday to use this in a customer but does anyone
> know how much data would we lose if there is an instance failure?
> 
> So far I have not seen this used in production
> 
> Thanks
> 
> --
> LSC
> 

--
http://www.freelists.org/webpage/oracle-l