Results 1 to 5 of 5
  1. #1
    Join Date
    Aug 2004
    Posts
    7

    Unanswered: Merge Replication problem....

    I created a new pull subscription and I noticed that the subscriber is downloading changes from the publisher (new rows or changes made on other subscribers) but is not uploading new info back to the publisher.

    I have been working with this type of replication for a year now and never have any problem like this.

    - The job succeeded always. but no changes are uploaded to the susbsciber.
    - Checking the merge agent history has 0 on inserts, deletes and updates on the susbcriber.
    - Publisher is running the same merge replication with other 42 subscribers without problems.
    - Windows 2000 Server (sp4) , Sql 2000 (sp3)
    - Sanpshot size is 12 Gigas , I don't want or can't affort to copy again the snapshot.

    Thank you for your help.

  2. #2
    Join Date
    Jan 2005
    Location
    TempDb
    Posts
    228
    Does your distribution database have the transactions that have not been applied to the Subscriber? If not, you have no option but to apply a snapshot - how you do that is dependent on what is missing and what is available. You can roll-your-own snapshot.

    Test a dummy insert on your Publisher and see what happens from Distribution to Subscription(s). It appears something is not running correctly on the Subscriber, and checking the Distributor will help you determine that.

    Finally, you may want to create a job that alerts when the difference between the date of the most recently inserted row in your most active article and GetDate() is > n hours.
    I love deadlines. I like the whooshing sound they make as they fly by. Douglas Adams

  3. #3
    Join Date
    Aug 2004
    Posts
    7
    Thank you for your suggestions.

    I described my problem incorrectly above in saying that I could upload my new data to the subscriber.

    The problem is that one of my 42 subscribers is receiving all and any changers that any of the 42 subscriber makes, but it does not sent it's new info to the publsher.

    So, it could receive changes but not send any upward.

    Sorry, for the confusion.

  4. #4
    Join Date
    Jan 2005
    Location
    TempDb
    Posts
    228
    My suggestions still apply - just work from the Subscriber back to the Publisher. Use whatever Distributor that Subscriber is using to communicate Updates back to the Publisher to see where the problem is.
    I love deadlines. I like the whooshing sound they make as they fly by. Douglas Adams

  5. #5
    Join Date
    Feb 2005
    Posts
    78
    If you find that any changes at the subscriber are not 'taking' i.e. they get overwritten from the publisher even when there are no changes to those particular records anywhere else, then you should check that you have set the subscription priority appropriately and not just left it as 'use publisher as proxy'. I speak from experience.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •