Re: Replication & read consistency

Suggestion:

Look at SharePlex software from Quest.
http://www.quest.com/shareplex-portal/index.asp

They're replication software is based on replicating archive logs and can be timed to replicate on your schedule. I just had a Quest engineer on site for several days to demo this product in a sandbox setup for my organization, and it appears to be a very good solution in comparison to Oracles product for our situation.

"Grant Fitzgerald" <gfitzger_at_hotmail.com> wrote in message news:cdf183bb.0206110110.441101b0_at_posting.google.com...
> Hi,
>
> I have two databases (let's call them 'A' and 'B'). A is my master
> database and B is simply a collection of snapshots for all the tables
> in A.
>
> The way I need this to work is as follows:
>
> Over a period of days several admin users update A with large amounts
> of data, committing as they go. I do not want the data to be
> replicated to B until the last change to A is made. When the changes
> to A are complete I want to refresh B. However, there are lots of
> users accessing B and I don't want them to see any of the new data
> until one final commit point at the end of the refresh.
>
> Does a manual refresh work like this (i.e. one final implicit commit
> at the end of the refresh) or does it update the tables as it goes (so
> users would see a mixture of old & new data)?
>
> FYI - I have all my snapshots in snapshot group which I refresh using
> DBMS_REFRESH.REFRESH
>
> Many thanks for any help you can give me.
>
> Cheers,
> Grant Fitzgerald
Received on Wed Jun 12 2002 - 02:39:17 CEST