September 1, 2011 at 1:03 pm
I am getting following error please guide
The Replication agent has not logged a progress in 10 minutes. This might indicates an unresponsive agent or high system activity, Verify that records are being replicated to the destination & that connections to the subscriber, publisher & Distributor are still running
Thank s
Nirav
September 1, 2011 at 1:15 pm
niravbhat (9/1/2011)
The Replication agent has not logged a progress in 10 minutes. This might indicates an unresponsive agent or high system activity, Verify that records are being replicated to the destination & that connections to the subscriber, publisher & Distributor are still running
And...???
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 1, 2011 at 1:19 pm
that was it .
that was only error getting
September 1, 2011 at 1:26 pm
And have you checked what the error message told you to check? (the piece I highlighted)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 2, 2011 at 12:18 am
There may be multiple cases for this issue. To come for proper conclusion, please verify the jobs correspoding to this replication setup and make sure that they are running..not hung.
If job doesnt seem to be running, try to stop it and rerun, sometimes it will solve the issue
If ur organization allows for REINITIALIZATION of replication, give a try.
If any of the above methods does not work out then, please post the error in the job related to this replication.
SQLforU
info@sqlforu.com
For online training on SQL Server and Sybase, please contact
contact@sqlforu.com
www.sqlforu.com
September 2, 2011 at 1:36 am
niravbhat (9/1/2011)
I am getting following error please guideThe Replication agent has not logged a progress in 10 minutes. This might indicates an unresponsive agent or high system activity, Verify that records are being replicated to the destination & that connections to the subscriber, publisher & Distributor are still running
Thank s
Nirav
What are the publisher, distributor and subscriber versions? I had seen it happening on one of my replications set from sql2000 to sql2008. It is also advisable to check the history of all the replication agents and also use the distributor database tables to find if there are any errors logged here.
Chandan
September 2, 2011 at 5:10 am
Hi,
What is your database size ? please check where is the delay ? publisher to distributer or dictributor to subscriper ? what kind of replication are you using ? if the size is small and it is out of business hours better REINTIALIZE it once , check the transaction volume in your database. if you can able to commit some transactions manually using the custom scripts pls do that to avoid the latency .. please dont REINTIALIZE when your system ( Database) is very busy and full loaded. bcz this makes your sysem very slow when snapshot statrs running. for this there might be many cases so check everything is running fine before doing something.
Reagrds
Raju
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply