Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Replication / September 2004

Tip: Looking for answers? Try searching our database.

Remove duplicate replica

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ingo - 16 Sep 2004 12:24 GMT
I once thought I had a corrupt replica on a remote
machine. So I removed this replica and substituted it by
another one and gave this replica exactly the same name as
its predecessor (I know this is a horrible sin, it was
still in those days when I didn't have the slightest clue
what replication means). Now I've got the problem that the
system table thinks that there are two replicas (with
different replica IDs). The trick with direct replication
with the removed replica doesn't work since it has exactly
the same path and name as the old replica, so it thinks it
is supposed to replicate with itself.

Does anyone have experience with this problem? Thanks!
Cheval - 20 Sep 2004 21:18 GMT
Do the same thing again, except for one extra step.
1) Replicate the data from the dup replica
2) Delete the Dup Replica
3) try to replicate to the Dup Replica (say yes to remove
from replica set)
4) Do three again until each duplicate is gone
5) Create new non-dup replica.
6) Done.

>-----Original Message-----
>I once thought I had a corrupt replica on a remote
[quoted text clipped - 11 lines]
>Does anyone have experience with this problem? Thanks!
>.
Ingo - 21 Sep 2004 09:43 GMT
I did pretty much exactly what you described, and it
worked (Yeah!). But there is one thing that concerns me:
In the system table "MSysReplicas" of the new replica in
place, the old dup replicas are properly marked as
removed. However, upon several rounds of synchronization
with other replicas within the set, these replicas didn't
take over this information in their system tables. Is this
information only locally stored? If not, what could be
wrong and do I have to fear negative implications?

>-----Originalnachricht-----
>Do the same thing again, except for one extra step.
[quoted text clipped - 27 lines]
>>
>.
Cheval - 21 Sep 2004 23:04 GMT
Well I've also wondered in the past what negative impact
these "Phantom" replicas could do, but as each replica has
a unique ID, the only problem I can see is viewing deleted
replicas in the replica set for the poor human might get
confusing. ie. It's more of a bother for you than the
replication system as such.

Unless of course I'm wrong and please correct me if so.

>-----Original Message-----
>I did pretty much exactly what you described, and it
[quoted text clipped - 42 lines]
>>
>.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.