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:27:31 +0530
Message-ID: <BBD944BCAC3AB4499DFBAFB1D8AF302001D3E328@BLRKECMSG11.ad.infosys.com>

Anjo, Folks

Qs 1 When using COMMIT_WRITE=BATCH,NOWAIT, After a database crash, if the respective Application has the capability to check within the database for

volume of transactions lost after complete recovery & re-play the same, Can the COMMIT_WRITE=BATCH,NOWAIT feature be used in such a case?

This basically refers to periodic Batch nature of Transactions which run with NO intermediate User intervention.

Anjo's reply - If the application can recover it self, yes why not.

Seek the following Clarification by citing a particular example:-

Our Banking Application runs the Interest Calculation batch Job for a SET of Accounts. If for any reason the Job gets aborted while underway, on re-starting the Application has the capability to check from within the Database & run the interest calculation for only those accounts of the set, whose calculation was still pending during the previous calculation run. Those accounts of the SET whose Interest Calculation was complete during the previous run are NOT subjected to re-run.

In such a case can COMMIT_WRITE=BATCH, NOWAIT be deployed in PRODUCTION environment for the respective batch job?

Thanks indeed

Received on Fri Sep 22 2006 - 04:57:31 CDT

Original text of this message

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