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

transaction replication distribution job issue Expand / Collapse
Posted Friday, April 11, 2014 2:48 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, April 14, 2014 11:30 AM
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.
Post #1561133
Posted Friday, April 11, 2014 4:25 PM

Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: 2 days ago @ 5:46 AM
Points: 3,998, Visits: 7,172
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 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) 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"
Post #1561146
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse