Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...
SQL Server Forum / Other Technologies / Replication / September 2006

Tip: Looking for answers? Try searching our database.

Agents hang on failure

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris - 28 Sep 2006 16:41 GMT
All servers SQL2000 Std Ed., sp4

Transactional Replication

Publisher in Hong Kong, distributor in Calif - subscriber in Calif

LogReader & Distr. agents on 2 minute schedule.

Connectivity lost to remote publisher, the Log Reader (job) gets to Step 3:
Detect nonlogged agent shutdown.  In Replication Monitor the Log Reader agent
displays 'Performing completion actions'.

The only option is to 'Stop Agent' - however it never stops, even after
hanging for 8 hours+ in this state - I never get the option 'Start Agent'
enabled.

I try to stop/start on Log Reader job itself - and nichts.

The only way to resolve, stop & restart SQL Services on distributor.

Any ideas how or why this is happening?

TIA,
Chris
Reply to this Message
Hilary Cotter - 28 Sep 2006 17:10 GMT
Log reader agents should run continuously as opposed to a scheduled basis,
also you should have local distributor - you shouldn't connect to a remote
distributor over the WAN.

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

> All servers SQL2000 Std Ed., sp4
>
[quoted text clipped - 22 lines]
> TIA,
> Chris
Reply to this Message
Paul Ibison - 29 Sep 2006 09:19 GMT
Chris,
you could enable logging of the log reader to try to get more info:
http://support.microsoft.com/?id=312292
It could be that the transaction log is huge and it is taking ages to read
through it. It could be that there is some blocking in the distribution
database which is stopping the log reader from completing (sp_who2 will give
info on this).
    Cheers,
         Paul Ibison SQL Server MVP, www.replicationanswers.com .
Reply to this Message
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.