/ * --- Ningoo (Ning Ge) Copyright 2004.12 --- * / I just went to work this morning, I found a log agent in synchronous replication: The process could not execute 'sp_replcmds' on 'ServerName'.
Some relevant information is found after searching online:
There is a bug before SQL Server 2000 SP2 can cause this error. http://support.microsoft.com/kb/q308865/
But my already hit SP3A, it should not be this reason.
Others say that they want to set the value of querytimeout in Agent Profiles, try ineffective.
View SQL Server Error Log, found the following record error: 9002, Severity: 17, State: 6the log file for database 'Servername' Is Full. Back Up The Transaction Log The Database to Free Up Some log space ..
Halo, is it short-term disabled space? I saw the LOG of the DB, there were 25g, and the weekend was too fast, and the entire disk space was used. SP_REPLCMDS to generate synchronization information, but the hard disk has no space, causing the error to occur.
Solution: Shrink the log, empty enough disk space backup log servername with no_logdbcc shrinkDatabase ('ServerName', TruncateOle ")
