Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Asynchronous Commit Feature of 10.2 - Basic Qs

RE: Asynchronous Commit Feature of 10.2 - Basic Qs

From: VIVEK_SHARMA <VIVEK_SHARMA_at_infosys.com>
Date: Fri, 22 Sep 2006 15:12:19 +0530
Message-ID: <BBD944BCAC3AB4499DFBAFB1D8AF302001D3E312@BLRKECMSG11.ad.infosys.com>

Anjo, Folks

If you could possibly Clarify Anjo's reply below?

Also I infer that Anjo reply means "YES" to my Question below (since an SCN would have been generated by the COMMIT at 10:00)

Qs 3 If multiple processes are running parallely & committing data with a related logical inter-dependency between them while doing updates, can the

same be maintained when using the Asynchronous commit feature? To Explain this in simpler words:-

Assume for 1 process COMMIT_WRITE is set to BATCH,NOWAIT.

Assume at 10:00 this process issues a Commit after updating a field value to say "A".

Assume that Oracle decides to write it to redo logs on Disk at 10:02.

Question - If at 10:01 ANOTHER process reads(SELECTs) the same field value, will it get the UPDATED field Value of "A"

Anjo's Reply - The redo is only used for recovery. You are confusing the SCN number. The current SCN and the snapshot scn (start of statement) dictate what you will see as commited or not.

Thanks indeed

Received on Fri Sep 22 2006 - 04:42:19 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US