Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Problems re adding expired subscriptions Expand / Collapse
Author
Message
Posted Tuesday, February 26, 2008 3:21 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, May 12, 2009 7:49 AM
Points: 46, Visits: 42
Hi, We have a merge replication setup that merge replicates audit info from 85 2k and 2k5 servers to 1 2k5 central server. The problem is, that replication stopped working on a number of the servers (not sure why) and by the time this was spotted, a number of the subscriptions had expired and had been cleared off by the replication tidy up job.

The problem is, when we try to re create the subscription we get the error:

Msg 14058, Level 16, State 1, Procedure sp_addmergesubscription, Line 381
Cannot create the subscription because the subscription already exists in the subscription database. Only one subscription to the same publication is allowed in each subscription database. Drop the subscription and add it again if necessary. If the problem persists, replication metadata might be incorrect; see Books Online for troubleshooting information.

The thing is, there appears to be no subscription for the server visible off the publication node and the subscription server has not entries in the subscribers node.

How do I reset things for this subscriber without loosing all the existing working subscriptions currently on the server. We've so far lost about 20 servers from the list.

Hope someone can help.

Post #460123
Posted Monday, March 3, 2008 7:25 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, May 12, 2009 7:49 AM
Points: 46, Visits: 42
I have found a way to fix this problem without having to drop and re create the whole publication / subscribers. In the sysmergereplication table on the publisher db, remove the row for the expired subscriber subscription.

delete from sysmergesubscriptions
where subscriber_server =

Once this row has been removed you can then re add the subscriber using sp_addmergesubscription setting the @sync_type = N'None' which will prevent any new un replicated data being lost on the subscriber.

This all appears to work but seems quite a scary way to fix things without using sys procedures to do the job for me.

Any thoughts from anyone?
Post #463128
Posted Monday, March 3, 2008 8:28 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, October 25, 2013 7:43 AM
Points: 1,384, Visits: 644
I have had that problem in the past

most of the time if i go to the subscriber and drop it there it works

2k5 lots of time will remove it from the publisher but leave stuff on the subscriber




Post #463174
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse