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

Home -> Community -> Usenet -> c.d.o.server -> Detailed replication explanation (e.g. locks)

Detailed replication explanation (e.g. locks)

From: Brian Rasmusson <br_at_belle.dk>
Date: 1997/09/08
Message-ID: <3413D804.5AA1BDFA@belle.dk>#1/1

Hi all,

Can any of you tell me how Oracle replication works on the lowest level. I would like to know when locks are set and freed, how many rows are locked when and why, and when the commit is issued.

We have developed an application running in a master + updatable snapshot environment, but experienced that the replication process blocked for out application on the snapshot site.

So.. If a large batch job updates e.g. 100.000 records on the master site, how are they actually replicated to the site? Does Oracle make one huge transaction (i have seen a refresh job run out of rollback space on other occasions) and a single commit, or does it commit rows one by one? Does it lock the entire table, all rows to be updated or one row at a time?

Hoping for a good explanation.

Best regards,

Brian

--

------------------------------------------------------------------------
Brian Rasmusson, Software engineer & analyst e-mail: brianr_at_belle.dk Belle Systems A/S web : www.belle.dk Network, Internet and communication specialists phone : +45 59442500
------------------------------------------------------------------------
Received on Mon Sep 08 1997 - 00:00:00 CDT

Original text of this message

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