June 22, 2018 at 7:26 am
Dear All,
The Repl-LogReader job is currently blocking distribution cleanup job sql; would there be a way of resolving the issue without restarting the service please?
Thank you in advance!
June 22, 2018 at 10:55 am
tt-615680 - Friday, June 22, 2018 7:26 AMDear All,
The Repl-LogReader job is currently blocking distribution cleanup job sql; would there be a way of resolving the issue without restarting the service please?
Thank you in advance!
You can try stopping the log reader agent for a bit of time and give the distribution clean up a chance to catch up. Then start the log reader agent again. Sometimes there is just so much in the queue that the distribution cleanup doesn't complete.
You can stop the agent in Replication Monitor. Go to the Agents tab and select Log Reader Agent from the Agent type drop down.
Or you can stop the job. It's the replication job with the category REPL-LogReader.
Sue
June 25, 2018 at 2:31 am
Thank you for your reply. I wanted to know if there is an implication in stopping the job which is why I haven't stopped it.
June 25, 2018 at 12:27 pm
tt-615680 - Monday, June 25, 2018 2:31 AMThank you for your reply. I wanted to know if there is an implication in stopping the job which is why I haven't stopped it.
The implication would be that the log reader agent wouldn't be reading and setting transactions to be replicated. The degree of impact depends on how active the publications are in terms of replicated transactions.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply