SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


transaction replication distribution job issue


transaction replication distribution job issue

Author
Message
dw_kishore
dw_kishore
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 23
Hi, today we received the alert that distribution agent was failed for transaction replication for one node. We have two subscribers.
Here is the error message, look like it is due to network hiccup. I have restarted the agent and replication caught in a minute. And there are NO bulk transactions that time

Error messages:
The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.


But network guys saying The Distribution Agent failure occurred before the network hiccup, there is a 10 minute gap between these two events. The network did not cause the Agent to fail.
Did anyone come across this type of problem? Please advise.
MyDoggieJessie
MyDoggieJessie
SSCertifiable
SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)

Group: General Forum Members
Points: 6646 Visits: 7391
In my experience, this isn't actually an error. It's more of a "Hey! I'm usually pretty busy, but I've got nothing to do right now...you should take a look!" or it's in the middle of a really large batch of replication commands (and it's just taking a long time to commit)....it could also be that there is a process blocking the replication spid that's currently running (very common).

Did you see any records in the [distribution].[dbo].[MSrepl_errors] table? If there was an actual error, it should be logged there or in your SQL Server Error logs...

You can change the heartbeat interval to be longer if you see this often (it just changes how frequently the check occurs).

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search