Groups | Blog | Home
all groups > sql server replication > september 2006 >

sql server replication : Agents hang on failure


Chris
9/28/2006 8:41:01 AM

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,
Hilary Cotter
9/28/2006 12:10:50 PM
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.

--
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



[quoted text, click to view]

Paul Ibison
9/29/2006 12:00:00 AM
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 .

AddThis Social Bookmark Button