changed server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Esther - 20 Sep 2007 15:00 GMT

I keep my replicated db on a shared drive and it has worked well for several
years. I just tried to sync some replicas and am getting an error: local or
anon replicas have to be sync'd with their designated hub.

When I look at the drop-down list in "sync now", the paths start with
<name>57vs\<path>. My current design master sits on <name>77vs1\<path>. The
<path> is the same for both after you get past this root directory. If I
change the path to 77vs1, I get the same 'designated hub' error.

We changed servers in June and I hadn't sync'd any of the existing replicas
until yesterday. BTW - When the new server came on line, they had copied the
file so we used the 'make this a design master' feature. I have created
some new replicas since the server change and they work as expected.

Do you think the server change the reason for this error? If this is the
reason, is it easy to explain in a nutshell? I know it 's not easy to FIX in
a nutshell but is there any hope since I can actually get to the tables in
the replicas.

Any feedback would be helpful.

Reply to this Message

David W. Fenton - 21 Sep 2007 00:52 GMT

> I keep my replicated db on a shared drive and it has worked well
> for several years. I just tried to sync some replicas and am
> getting an error: local or anon replicas have to be sync'd with
> their designated hub.

Anonymous replicas are simply a bad idea:

http://trigeminal.com/usenet/usenet027.asp?1033

I have never been tempted to use them, as they seem designed
entirely to solve a problem that is caused by mis-using replication
in the first place.

> When I look at the drop-down list in "sync now", the paths start
> with
[quoted text clipped - 8 lines]
> master' feature. I have created some new replicas since the
> server change and they work as expected.

In preparation for the server move you should have:

1. synched all anonymous replicas with their parent hubs.

2. used the MoveReplica command (in Replication Manager or in the
TSI Synchronizer -- it's one of the chief ommissions in JRO that
makes JRO so useless) to move the hub and DM from the old server to
the new one.

3. then killed all the anonymous replicas and created new replicas
to replace them.

> Do you think the server change the reason for this error?

Yes, of course. Anonymous replicas know only their designated hub.
When that hub ceases to exist, they are dead in the water and can
never synch again with anything.

> If this is the
> reason, is it easy to explain in a nutshell? I know it 's not
> easy to FIX in a nutshell but is there any hope since I can
> actually get to the tables in the replicas.

I really don't understand why anyone would implement anonymous
replicas.

Signature

David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Reply to this Message

Esther - 21 Sep 2007 13:34 GMT

Thanks David. I'm not sure where I'm going to take this from here but at
least I know it was the server change that caused the error. BTW - I didn't
set up the system but I believe they are local replicas. It's just the error
message that said "Local or anonymous..." Thanks so much for your quick
reply. Esther

> > I keep my replicated db on a shared drive and it has worked well
> > for several years. I just tried to sync some replicas and am
[quoted text clipped - 47 lines]
> I really don't understand why anyone would implement anonymous
> replicas.

Reply to this Message

David W. Fenton - 21 Sep 2007 21:54 GMT

> I'm not sure where I'm going to take this from here but at
> least I know it was the server change that caused the error. BTW
> - I didn't set up the system but I believe they are local
> replicas. It's just the error message that said "Local or
> anonymous..." Thanks so much for your quick reply.

Well, a full or partial replica ought to be able to synch. You
should be able to manually force the synch with the new hub replica,
either in code or, if you can do direct synchs, through the Access
UI.

That is, a replica doesn't have to know the name of the partner
replica to synch with, as long as you provide it to it.

Signature

David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Reply to this Message