April 11, 2014 at 2:48 pm
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.
April 11, 2014 at 4:25 pm
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; Theyll drag you down to their level and beat you with experience
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply