Does anyone know how to keep sequences in synch between a replicator and a
replicatee?
I would like to set up two servers: one that receives modifications and
another that is read only. The server that receives data modifications from
clients will replicate data over to the second server. The second server
functions as a read only database allowing clients to search for data for
load balancing and as a hot stand by for the first server in case of
failure.
The problem is that the first server will be generating unique identifiers
using sequences. That data gets pushed to the second database fine. There
will be sequences in the second server as well. How does Oracle handle
keeping sequences for both publisher and subscriber?
I'd like to be able to have the second database server allow data
modifications and generate identifiers should the first (publisher) server
fail. Clients will be able to connect to the second database upon detecting
that the first server failed. The second server would allow updates at that
point and serve as the primary update server and clients will need to
connect to that second server in case of failure on the first server.
Is this possible? If so, how is this done? Thanks!
Received on Wed Nov 24 1999 - 00:00:00 CET
