Re: Asynchronous Commit in Oracle Database 10g R2

"VC" <boston103_at_hotmail.com> wrote:

<snip asynchronous commits>

> Could you please comment on how this optimization does not create a
> possibility for data loss ?

Who says it doesn't? Of course there is the possibility of data loss. But then again, if your A/D converter suffers a buffer overrun because the app spent too much time waiting for a log sync, that is also a possibility for data loss. Life's a bitch, then you die.

> (An application thinks that a transaction has
> committed while in fact it did not, and a crash occurs ...)

Since the thing which is doing the commit in the tight loop is a PLSQL block running on the same database server, then the application's "thought process" doesn't survive the crash any better than its commits did. Therefore, the application can't "think" that it committed the transaction--either it can reconstruct exactly what it needs to by looking at what did get truly committed, or it simply has no idea what happened prior to the lights going out. If this is a problem, you shouldn't be commiting in the loop anyway, asynchronously or not.

Xho

-- 
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service                        $9.95/Month 30GB