all groups > sql server replication > november 2004 >
You're in the

sql server replication

group:

Log Reader Agent fails: could not execute sp_MSadd_repl_commands27



Log Reader Agent fails: could not execute sp_MSadd_repl_commands27 MichelleM
11/4/2004 2:18:06 PM
sql server replication: An unusually large number of updates were processed against a database that
we replicate. Normally, we see no issues with replication. However, we had
several Log Reader Agent failures with the error message mentioned above. I
updated the QueryTimeout parameter from 300 to 750 after finding a
recommendation for that change. Another failure occurred, and the Log Reader
Agent was restarted. It "appeared" to be running for the next 9 hrs
(although replication seemed to be behind by 2-3 hrs); and then another
failure. I then updated the QueryTimeout parameter to 1000; and within 5
minutes replication was caught up.

My question: is it possible that the increase of the QueryTimeout resolved
the issue, or could it have just been coincidental that the change was made
Re: Log Reader Agent fails: could not execute sp_MSadd_repl_commands27 IBI
11/4/2004 7:41:35 PM
It certainly sounds like Query Timeout issue,

[quoted text, click to view]

Log Reader Agent fails: could not execute sp_MSadd_repl_commands27 Paul Ibison
11/5/2004 1:33:00 AM
Have a look at the error details to get more info. It
could have been a querytimeout issue. On the other hand
this morning one of my log reader agents reports:
"The SQL Server cannot obtain a LOCK resource at this
time. Rerun your statement when there are fewer active
users or ask the system administrator to check the SQL
Server lock and memory configuration.
(Source: servername (Data source); Error number: 1007)"
This is the detailed error message from exactly the same
error as the subject of your message and is not related
to timeouts per se, but to a longstanding issue where
there is a series of blocking jobs which exceeds the
total lock allocation.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com

(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
RE: Log Reader Agent fails: could not execute sp_MSadd_repl_commands27 MichelleM
11/5/2004 6:48:12 AM
I didn't see detail to the final error message, but then did with the
previous message:
Timeout expired
(Source: ODBC SQL Server Driver (ODBC); Error number: 1003)
---------------------------------------------------------------------------------------------------------------
IDistPut Interface has been shut down.
(Source: (Agent); Error number: 2000)
-------------------------------------------------------------------

So I'm assuming that "Timeout Expired" is the root cause and means the
QueryTimeout parameter needed to be increased.
Michelle

[quoted text, click to view]
RE: Log Reader Agent fails: could not execute sp_MSadd_repl_commands27 Paul Ibison
11/5/2004 6:57:28 AM
Michelle,
in that case I fully agree. I have had to increase this
parameter myself for the same reason. I have used the
value 0 which is reported to mean infinity, although
there is a little contention about this. In your tests,
each time you were increasing the QueryTimeout and
running the logreader, I believe more records were being
removed from the log, so the fact that after the last
increase the log was read in 5 minutes was probably a
little misleading. If it happens again, you can run
sp_replshowcmds to be sure what is happening.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com

(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
AddThis Social Bookmark Button