SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The process could not execute ''sp_replcmds'' on PRODUCTION


The process could not execute ''sp_replcmds'' on PRODUCTION

Author
Message
gardengnome
gardengnome
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
Points: 7 Visits: 0
Sorry to add to an old post but hopefully it helps.

I had the same problem today after REORGANIZING a ton of heavily fragmented indexes (rebuild not an option).

To fix I had to go into Enterprise Mgr..... find the agent under replication->log reader agent
Right click, choose agent profiles.

This allowed me to create a new profile with a larger timeout value and i had to also set ReadBatchSize to 1

After doing this replication is now running again, it just took longer than normal to catch back up but this has fixed the problem for me. I will change the ReadBatchSize parameter back to 500 after a few hours but thought I'd share my experience with this issue.

Thanks.
Nneka Ilene
Nneka Ilene
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 42
Thank you. Your answer just saved me three hours. It worked!

Regards
Nneka
cwilliams-1119036
cwilliams-1119036
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 15
Sorry this is such a late post but we just started having this same issue on Sundays when our REORG's run. Any ideas on why reorganizing causes this to happen? I will try your fix next time unless I can find what is causing this to happen and can prevent it.
mark.pointon
mark.pointon
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 192
HI, I'd thought that I'd add my experience on this. We experienced the same issue with the log reader agent in Sql 2000, caused by a now outage over the weekend. Instead of amending the -readbatchsize to 1, I amend from 500 to 100, which also worked. I suppose it depends on the severity of the backlog. So you don't need to reduce all the way down to single batch sizes.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search