Post reply

Latency critical, but no undistributed transactions listed

  • October 6, 2009 at 4:19 pm

    #211695

    I have a transactional publication set up in sql 2005 SP2. It has been running ok, suddenly, latency is "critical" (6 hours) when I look at undestributed transactions for the subscriptions (2 of them). querying the subscriber shows that transactions stopped being applied 6 hours ago. Is there any way to catch up?

    showing syncronization status displays "99 transaction(s) with 100 command(s) were delivered.' so everything seems ok. But it's obviously not. Not sure where to look.

    Any help?

  • October 7, 2009 at 6:46 am

    #1062733

    Try restarting the distribution Job.

    -Roy

  • October 7, 2009 at 2:04 pm

    #1063055

    Thanks,

    The jobs stopped and started successfully, but still not applying transactions. When this has happened in the past, we have had to reinitialize the subscriptions. Is this the only way to get around this? I can't even seem to figure out why it got into this state Any other ideas?

  • October 7, 2009 at 2:27 pm

    #1063076

    Only twice did I get this issue. One got fixed when we restarted the distribution agent and the other was when we ran a delete script on the subscriber. Therefore some of the articles were not getting replicated and the others were. We had to drop the subscription and re add it.

    -Roy

  • October 7, 2009 at 2:53 pm

    #1063093

    OK, thanks! And drop and readd of subscription will ALways cause reinitialize correct?

  • October 7, 2009 at 3:27 pm

    #1063113

    Unless otherwise specified. You can always say not to synchronize. That is it will not create a snap shot. It will assume that the data is already available.

    -Roy

  • October 14, 2009 at 9:00 am

    #1065748

    Have you tried dropping a token and seeing if it makes it through OK?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply