Re: Usage of COMMIT NOWAIT, BATCH

Hi Jonathan

I forgot to mention that this is a insert intensive application so 3 seconds would not apply I guess. The insert rate is around 1000 to 2000 per seconds.

I guess the upper bound would be

1/3 log buffer
3 seconds
when the log buffer is full

no?

Thanks

--
LSC





On 2/2/08, Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk> wrote:


>

>

> 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_at_gmail.com>

> To: <hkchital_at_singnet.com.sg>

> Cc: <oracle-l_at_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

>

>

>


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