Simple,Clear and Superb explanation.
Thanks Arup.
-Original Message-
Nanda
Sent: Wednesday, November 19, 2003 1:10 AM
To: Multiple recipients of list ORACLE-L
VirVit,
You haven't specified Oracle version and your tolerance for data loss. If
you can afford to lose the data in the most
Verification was easy. We just powered down the primary machine, changed the
db name in the external table, drop the replication on the backup server and
restart the application. Everything worked fine. After 2-3 days, over the
weekend, we rebuilt the replication again.
Yechiel Adar
Mehish
-
We are doing exactly that. We use multi master synchronous replication. In
case the regular server dies, we drop replication from the backup machine.
Change one parameter in the application ini file (what db name to use in
connections), start the application again. About 5 minutes turn around
Yechiel - So how do you verify your backup environment? My gut feeling is
that simpler systems are less prone to catastrophe, and multimaster
replication definitely adds a lot of pieces compared to conventional
backups.
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original
VirVit,
You haven't specified Oracle version and your tolerance for data loss. If
you can afford to lose the data in the most current redo log file, then I
would suggest 9i Data Guard in maximum performance mode (or Standby in 8i)
solution over the MM replication. The DG solution does not affect
Andrey,
Don't even think about implementing this until you've
read the manuals and thoroughly understand the
concepts. Replication can be very unforgiving when
you don't properly design and configure it. You may
also find that your application is not even suited for
it.
- Is it a must for
Dear gurus !
I need to implement multimaster replication (asynchronous) among 2
databases.
A couple of general questions before i start :
- Is it a must for the 2 DBs to be of the same version (release) ?
- Is it a must for the 2 DBs to run on the same O/S, hardware etc ... ?
- Do U have to
Nihar,
Don't remove the network link!!
O.KI'm not a replication guru, but my thoughts are that the way
replication is setup, the commit can only happen if the data can be
replicated as it should. If there is no network connectivity, the instance
cannot get to one of the other required
Hi!
Well, i am not going to remove the link but What if the internet
connectivity fails. My DB servers are at different locations and i am doing
it through WAN link .Is there any way to queup the data till links come up.
thanks
-Nihar
-Original Message-
Sent: Tuesday, May 22, 2001
Nihar,
This is not normal. Asynchronous propagation
populates the deferred transactions queues which are
then pushed at a later time, so the only thing that
should happen when network connectivity is lost is
that the job pushing the queues will fail. Once
connectivity is re-established the job
10 matches
Mail list logo
