Hi. I have a split DB I have used for a few years now. I replicate the backend to a couple of other replicas. I have recently changed this and now have one place to replicate to only. The problem is that the other files are still in the Synchronize list. When I try to sync to the files that don't exist anymore I get the message saying that these files no longer exist, I click OK then I get another message saying that the file has been removed from the replica set and won't be reflected until I close and reopen the DB. I do this and the replica is still there. How do I get rid of it?
Replica's that no longer exist can't be removed
- Thread starter rmtimmah
- Start date
dfenton
AWF VIP
- Local time
- Today, 12:00
- Joined
- May 22, 2007
- Messages
- 469
You should check the MSysReplicas table to see exactly how many replicas there are with the path/filename/UNC path that you're trying to delete. In certain circumstances I've never figured out, it takes as many attempted synchs to completely delete a replica from the list as there are records for that replica in MSysReplicas. That is, the failed synch doesn't delete all the replicas with the same name, it just deletes one of them each time.
For instance, if your dead replica is called "C:\MyDeadReplica.mdb" on machine MYPC, you might find 10 records in MSysReploicas with that name/path on that particular PC. That means you have to attempt the synch 10 times.
Also, different replicas may have different records of different replicas in them, and you may need to do this from multiple records.
It's something of a mystery, I've found, but repeated synching with the dead replica will eventually delete all the replicas. You may need to synch around your full replica set for it to take effect, and it may also require a compact before it fully "takes."
Last of all, DON'T DO THIS AGAIN. Use the TSI Synchronizer and do a legal MoveReplica command, instead. Creating dead replicas endangers the health and reliability of your replica set and that's something you never want to do on purpose.
For instance, if your dead replica is called "C:\MyDeadReplica.mdb" on machine MYPC, you might find 10 records in MSysReploicas with that name/path on that particular PC. That means you have to attempt the synch 10 times.
Also, different replicas may have different records of different replicas in them, and you may need to do this from multiple records.
It's something of a mystery, I've found, but repeated synching with the dead replica will eventually delete all the replicas. You may need to synch around your full replica set for it to take effect, and it may also require a compact before it fully "takes."
Last of all, DON'T DO THIS AGAIN. Use the TSI Synchronizer and do a legal MoveReplica command, instead. Creating dead replicas endangers the health and reliability of your replica set and that's something you never want to do on purpose.
Similar threads
