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

REPLICATION ISSUE Expand / Collapse
Author
Message
Posted Thursday, September 1, 2011 1:03 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, October 17, 2014 12:49 PM
Points: 20, Visits: 272
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
Post #1168869
Posted Thursday, September 1, 2011 1:15 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:37 PM
Points: 40,210, Visits: 36,619
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1168877
Posted Thursday, September 1, 2011 1:19 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, October 17, 2014 12:49 PM
Points: 20, Visits: 272
that was it .

that was only error getting
Post #1168879
Posted Thursday, September 1, 2011 1:26 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:37 PM
Points: 40,210, Visits: 36,619
And have you checked what the error message told you to check? (the piece I highlighted)


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1168887
Posted Friday, September 2, 2011 12:18 AM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, December 9, 2011 11:45 AM
Points: 14, Visits: 31
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
Post #1169037
Posted Friday, September 2, 2011 1:36 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Tuesday, September 30, 2014 11:40 PM
Points: 466, Visits: 1,923
niravbhat (9/1/2011)
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


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
Post #1169063
Posted Friday, September 2, 2011 5:10 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, October 22, 2014 7:01 PM
Points: 195, Visits: 377
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
Post #1169144
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse