|
|
You're in the
sql server replication
group:Prcess could not execute 'sp_MSadd_repl_commands27hp'
sql server replication:
Hello all, Our log reader agent is failing at times with the error "The process could not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'... We have custom distribution agents that have -CommitBatchSize = 500 and -CommitBatchThreshold = 1000... I'm also noticing that our distribution agent cleanup agent progressively takes longer through our peak. From 10 minutes to close to an hour... So I'm thinking we are having contention between the distribution db cleanup and maybe our -CommitBatchSize... Any recommendations?
Stop the distribution agent and run the log reader agent again. You may need
to enable logging and post the results back here if the condition does not clear. -- 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] "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message news:8A5EB566-D904-4335-ABF8-9BA387671F73@microsoft.com... > > Hello all, > > Our log reader agent is failing at times with the error "The process could > not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'... > > We have custom distribution agents that have -CommitBatchSize = 500 and > -CommitBatchThreshold = 1000... > > I'm also noticing that our distribution agent cleanup agent progressively > takes longer through our peak. From 10 minutes to close to an hour... > > So I'm thinking we are having contention between the distribution db > cleanup > and maybe our -CommitBatchSize... > > Any recommendations? > > Thanks!
OK... Here is what is in the log... It goes from working fine to throwing
errors to working fine again: ------------------------------------------------------- .... Status: 16384, code: 20007, text: 'No replicated transactions are available.'. Status: 2, code: 1003, text: 'The process could not execute 'sp_MSadd_repl_commands27hp' on 'DistServerName'.'. The process could not execute 'sp_MSadd_repl_commands27hp' on 'DistServerName'. Status: 2, code: 1003, text: 'Timeout expired'. Status: 0, code: 22020, text: 'Batches were not committed to the Distributor.'. The agent failed with a 'Retry' status. Try to run the agent at a later time. Status: 4096, code: 20024, text: 'Initializing'. Status: 4, code: 20051, text: 'Delivering replicated transactions'. Status: 2, code: 1003, text: 'The process could not execute 'sp_MSadd_repl_commands27hp' on 'DistServerName'.'. The process could not execute 'sp_MSadd_repl_commands27hp' on 'DistServerName'. Status: 2, code: 1003, text: 'Timeout expired'. Status: 0, code: 2000, text: 'IDistPut Interface has been shut down.'. The agent failed with a 'Retry' status. Try to run the agent at a later time. Status: 4096, code: 20024, text: 'Initializing'. Status: 4, code: 20051, text: 'Delivering replicated transactions'. .... ------------------------------------------------------- Thanks! Michael [quoted text, click to view] "Hilary Cotter" wrote:
> Stop the distribution agent and run the log reader agent again. You may need > to enable logging and post the results back here if the condition does not > clear. > > -- > 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 > > > > "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message > news:8A5EB566-D904-4335-ABF8-9BA387671F73@microsoft.com... > > > > Hello all, > > > > Our log reader agent is failing at times with the error "The process could > > not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'... > > > > We have custom distribution agents that have -CommitBatchSize = 500 and > > -CommitBatchThreshold = 1000... > > > > I'm also noticing that our distribution agent cleanup agent progressively > > takes longer through our peak. From 10 minutes to close to an hour... > > > > So I'm thinking we are having contention between the distribution db > > cleanup > > and maybe our -CommitBatchSize... > > > > Any recommendations? > > > > Thanks! > >
At the time the below error occured, the "Distribution clean up: distribution" job was running: ------------------------------------------------------------------------------------- .... Status: 2, code: 1003, text: 'The process could not execute 'sp_MSadd_repl_commands27hp' on 'ANETREPUBVSQL1F'.'. The process could not execute 'sp_MSadd_repl_commands27hp' on 'DistServerName'. Status: 2, code: 1003, text: 'Timeout expired'. Status: 0, code: 22020, text: 'Batches were not committed to the Distributor.'. The agent failed with a 'Retry' status. Try to run the agent at a later time. .... ------------------------------------------------------------------------------------- As I noticed before, our distribution cleanup takes 30-50 minutes to complete during peak traffic. Thanks, Michael [quoted text, click to view] "Hilary Cotter" wrote:
> Stop the distribution agent and run the log reader agent again. You may need > to enable logging and post the results back here if the condition does not > clear. > > -- > 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 > > > > "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message > news:8A5EB566-D904-4335-ABF8-9BA387671F73@microsoft.com... > > > > Hello all, > > > > Our log reader agent is failing at times with the error "The process could > > not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'... > > > > We have custom distribution agents that have -CommitBatchSize = 500 and > > -CommitBatchThreshold = 1000... > > > > I'm also noticing that our distribution agent cleanup agent progressively > > takes longer through our peak. From 10 minutes to close to an hour... > > > > So I'm thinking we are having contention between the distribution db > > cleanup > > and maybe our -CommitBatchSize... > > > > Any recommendations? > > > > Thanks! > >
Stop the distribution clean up task until your log reader has processed all
of your commands in the log. Set readbatchsize to 500 and the querytimeout and log timeout to something large - I would try 300. These settings are for your log reader agent. -- Hilary Cotter 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] "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message news:F303B3EA-3B82-4F6B-AF9B-23386530C0F9@microsoft.com... > > At the time the below error occured, the "Distribution clean up: > distribution" job was running: > ------------------------------------------------------------------------------------- > ... > Status: 2, code: 1003, text: 'The process could not execute > 'sp_MSadd_repl_commands27hp' on 'ANETREPUBVSQL1F'.'. > The process could not execute 'sp_MSadd_repl_commands27hp' on > 'DistServerName'. > Status: 2, code: 1003, text: 'Timeout expired'. > Status: 0, code: 22020, text: 'Batches were not committed to the > Distributor.'. > The agent failed with a 'Retry' status. Try to run the agent at a later > time. > ... > ------------------------------------------------------------------------------------- > > As I noticed before, our distribution cleanup takes 30-50 minutes to > complete during peak traffic. > > Thanks, > > Michael > > > > > "Hilary Cotter" wrote: > >> Stop the distribution agent and run the log reader agent again. You may >> need >> to enable logging and post the results back here if the condition does >> not >> clear. >> >> -- >> 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 >> >> >> >> "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message >> news:8A5EB566-D904-4335-ABF8-9BA387671F73@microsoft.com... >> > >> > Hello all, >> > >> > Our log reader agent is failing at times with the error "The process >> > could >> > not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'... >> > >> > We have custom distribution agents that have -CommitBatchSize = 500 and >> > -CommitBatchThreshold = 1000... >> > >> > I'm also noticing that our distribution agent cleanup agent >> > progressively >> > takes longer through our peak. From 10 minutes to close to an hour... >> > >> > So I'm thinking we are having contention between the distribution db >> > cleanup >> > and maybe our -CommitBatchSize... >> > >> > Any recommendations? >> > >> > Thanks! >> >> >>
The default Log Reader agent profile has a -ReadBatchSize of 500 and a
-QueryTimeout of 300 already... So when you say "log timeout to something large - I would try 300", are you meaning the QueryTimeout? Again, FYI... This is SQL 2000. Anyway, I upped the QueryTimeout to 600 and I'm still getting the timeout... Thanks, Michael [quoted text, click to view] "Hilary Cotter" wrote:
> Stop the distribution clean up task until your log reader has processed all > of your commands in the log. Set readbatchsize to 500 and the querytimeout > and log timeout to something large - I would try 300. These settings are for > your log reader agent. > > -- > Hilary Cotter > > 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 > > > > "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message > news:F303B3EA-3B82-4F6B-AF9B-23386530C0F9@microsoft.com... > > > > At the time the below error occured, the "Distribution clean up: > > distribution" job was running: > > ------------------------------------------------------------------------------------- > > ... > > Status: 2, code: 1003, text: 'The process could not execute > > 'sp_MSadd_repl_commands27hp' on 'ANETREPUBVSQL1F'.'. > > The process could not execute 'sp_MSadd_repl_commands27hp' on > > 'DistServerName'. > > Status: 2, code: 1003, text: 'Timeout expired'. > > Status: 0, code: 22020, text: 'Batches were not committed to the > > Distributor.'. > > The agent failed with a 'Retry' status. Try to run the agent at a later > > time. > > ... > > ------------------------------------------------------------------------------------- > > > > As I noticed before, our distribution cleanup takes 30-50 minutes to > > complete during peak traffic. > > > > Thanks, > > > > Michael > > > > > > > > > > "Hilary Cotter" wrote: > > > >> Stop the distribution agent and run the log reader agent again. You may > >> need > >> to enable logging and post the results back here if the condition does > >> not > >> clear. > >> > >> -- > >> 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 > >> > >> > >> > >> "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message > >> news:8A5EB566-D904-4335-ABF8-9BA387671F73@microsoft.com... > >> > > >> > Hello all, > >> > > >> > Our log reader agent is failing at times with the error "The process > >> > could > >> > not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'... > >> > > >> > We have custom distribution agents that have -CommitBatchSize = 500 and > >> > -CommitBatchThreshold = 1000... > >> > > >> > I'm also noticing that our distribution agent cleanup agent > >> > progressively > >> > takes longer through our peak. From 10 minutes to close to an hour... > >> > > >> > So I'm thinking we are having contention between the distribution db > >> > cleanup > >> > and maybe our -CommitBatchSize... > >> > > >> > Any recommendations? > >> > > >> > Thanks! > >> > >> > >> > >
OK... I upped the QueryTimout to 1800 and I got the error "The agent is
suspect. No response within last 10 minutes."... Thanks, Michael [quoted text, click to view] "BATMAN" wrote:
> The default Log Reader agent profile has a -ReadBatchSize of 500 and a > -QueryTimeout of 300 already... > > So when you say "log timeout to something large - I would try 300", are you > meaning the QueryTimeout? Again, FYI... This is SQL 2000. > > Anyway, I upped the QueryTimeout to 600 and I'm still getting the timeout... > > Thanks, > > Michael > > > > "Hilary Cotter" wrote: > > > Stop the distribution clean up task until your log reader has processed all > > of your commands in the log. Set readbatchsize to 500 and the querytimeout > > and log timeout to something large - I would try 300. These settings are for > > your log reader agent. > > > > -- > > Hilary Cotter > > > > 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 > > > > > > > > "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message > > news:F303B3EA-3B82-4F6B-AF9B-23386530C0F9@microsoft.com... > > > > > > At the time the below error occured, the "Distribution clean up: > > > distribution" job was running: > > > ------------------------------------------------------------------------------------- > > > ... > > > Status: 2, code: 1003, text: 'The process could not execute > > > 'sp_MSadd_repl_commands27hp' on 'ANETREPUBVSQL1F'.'. > > > The process could not execute 'sp_MSadd_repl_commands27hp' on > > > 'DistServerName'. > > > Status: 2, code: 1003, text: 'Timeout expired'. > > > Status: 0, code: 22020, text: 'Batches were not committed to the > > > Distributor.'. > > > The agent failed with a 'Retry' status. Try to run the agent at a later > > > time. > > > ... > > > ------------------------------------------------------------------------------------- > > > > > > As I noticed before, our distribution cleanup takes 30-50 minutes to > > > complete during peak traffic. > > > > > > Thanks, > > > > > > Michael > > > > > > > > > > > > > > > "Hilary Cotter" wrote: > > > > > >> Stop the distribution agent and run the log reader agent again. You may > > >> need > > >> to enable logging and post the results back here if the condition does > > >> not > > >> clear. > > >> > > >> -- > > >> 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 > > >> > > >> > > >> > > >> "BATMAN" <BATMAN@discussions.microsoft.com> wrote in message > > >> news:8A5EB566-D904-4335-ABF8-9BA387671F73@microsoft.com... > > >> > > > >> > Hello all, > > >> > > > >> > Our log reader agent is failing at times with the error "The process > > >> > could > > >> > not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'... > > >> > > > >> > We have custom distribution agents that have -CommitBatchSize = 500 and > > >> > -CommitBatchThreshold = 1000... > > >> > > > >> > I'm also noticing that our distribution agent cleanup agent > > >> > progressively > > >> > takes longer through our peak. From 10 minutes to close to an hour... > > >> > > > >> > So I'm thinking we are having contention between the distribution db > > >> > cleanup > > >> > and maybe our -CommitBatchSize... > > >> > > > >> > Any recommendations? > > >> > > > >> > Thanks! > > >> > > >> > > >> > > > >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |