June 6, 2005 at 7:44 am
In a merge publication, with merge agents running in continuous mode at distribuitor, sometimes (once at 2-4 weeks) one of subscriptions is deleted and the data is no more replicated at this subscriber.
the setting of " subscription expire and are dropped if not syncronized" is 8 days.
the link between publisher/distribuitor and subscriber is down for 2-3 times/day (the subscribber is offline or the vpn is down).
I don't know other setting for dropping a subscription- ex. after a number o retries (200,300 per total) or something like this?
Where I can find the reason for dropped subscriptions?
thanks.
June 7, 2005 at 9:15 am
I suspect the connection breaks and the continous agent is sitting there in a failed state waiting for a manual stop/start to reconnect it to the subscriber. After a server restart some weeks later, it reconnects, realizes the subscription has expired, and performs a reinitialization or the subscription.
I'd suggest changing to a scheduled push/pull instead of continous so that when the link is down it will restart it self some time later. There is some added overhead vs continous, but you'll find this worth it if it solves your problem.
June 8, 2005 at 1:27 am
the link is never down more than 1 day (2-3 hours in fact,never more than 1 day). And I need data replicated very often.
I have a job running every 10 min: if the merge agent is not running and I have connection with subscriber the agent will be started.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply