?
Solved

Replication Problem

Posted on 2001-07-17
3
Medium Priority
?
329 Views
Last Modified: 2013-12-18
Hello everyone,

I have 2 replicas of a database which reside on 2 servers on 2 different domains. When I replicate the database, the replication is acting in a very strange way, which giving me strange results, for example..

1. When there is new documents added to one of the replicas, it is not being added to the other replica after replication.
2. Some documents are being duplicated, in which the other copy appears as "replica or save conflict" even if the documents have not been changed.


I tried to replicate the database by using a local replica, in which I start replicating the local replica with one of the servers then replicate it with the other server. But that did not solve the problem!!
I made sure that "Merge replica conflict" option is ticked from the form properties. But this did not help either!!

So what else can be checked?
Any ideas?!!

Thanx in advance,
Areej
0
Comment
Question by:Areej
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 24

Accepted Solution

by:
HemanthaKumar earned 200 total points
ID: 6291488
Checkw whether you are using selective replication and neglecting new documents by using @isnoewdoc function.

Secondly, the replication conflict can occur for various reasons, like some user or agent has tried to change the same field of the document in two replicas and system is wondering which is what ?

Replication conflict flag will work only when two documents were modified at same time but two different fields are modified then the copy is merged.

So check what edits happened on the docs

~Hemanth
0
 
LVL 13

Expert Comment

by:CRAK
ID: 6292644
I agree with Hemanth: check if there are any agents saving the documents, causing replication/save conflicts.

Regarding your 1st problem: It might happen if the server's date/time settings are not correct, or if they have been modified.

Example:
Mid 1999 (lets say, in june) people were testing for the Y2K-bug. Servers dates were shifted to Dec 31, 1999 and left for a while to see what happened. When such servers performed a replication before the date was set back to normal, the software (databse) still remembered it had already replicated on Dec 31. Modifcations made in July were not replicated: the database was already up-todate for another few months!

Back then it could be solved by selecting the database(s), choosing File > Replication > Settings > 3rd icon (other) and checking the date under "Only replicate incoming documents saved or modified after". You'd have to do so on all replicas and adjust if neccessary.
0
 

Author Comment

by:Areej
ID: 6332236
Thanks a lot for both of u. U r right, I found one agent that modifying the same field in both replicas.

Thanks again
Areej
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For beginners of Lotus Notes user this is important to know about the types of files and their location supported by IBM Notes. Mostly users are unaware about how many file types are created and what their usages are. This Article is fully dedicated…
Sometimes clients can lose connectivity with the Lotus Notes Domino Server, but there's not always an obvious answer as to why it happens.   Read this article to follow one of the first experiences I had with Lotus Notes on a client's machine, my…
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question