February 18, 2009 at 2:19 am
Hi All, While doing a transactional replication i got the following error in the log reader agent status:
"The process could not execute 'sp_repldone/sp_replcounters' on 'servername'.
and the synchronysation status gave the error :"The concurrent snapshot for publication 'publication name' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for.."
While the snap shot is being generated.
I executed sp_repldone on the publication database yet no improvement.
After deleting the replication when i run the replication script again then in 2nd or 3rd attempts it gets ok. Can any one please help me on this...
February 18, 2009 at 8:30 am
ritesh (2/18/2009)
Hi All, While doing a transactional replication i got the following error in the log reader agent status:"The process could not execute 'sp_repldone/sp_replcounters' on 'servername'.
and the synchronysation status gave the error :"The concurrent snapshot for publication 'publication name' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for.."
While the snap shot is being generated.
I executed sp_repldone on the publication database yet no improvement.
After deleting the replication when i run the replication script again then in 2nd or 3rd attempts it gets ok. Can any one please help me on this...
you should not be executing "sp_repldone" manually.
This is a very specialized operation.
You should recreate replication!
* Noel
May 4, 2009 at 4:06 am
how to stop those "sp_replcmds" things?me get such error that could not proccess "sp_replcmds" on "server name"
May 4, 2009 at 8:45 am
This usually happens due to resource contention on the server. Verify if you have a very high number of locks in distribution DB.
Also ensure that the timeout values for your log-reader is appropriate.
* Noel
May 5, 2009 at 11:38 am
goto agent profile->
Create new profile with:
log reader -QueryTimeout =10000...
re-run the log reader this will work.
HTH.
Thanx.
Thanx.
Vinay
http://rdbmsexperts.com/Blogs/
http://vinay-thakur.spaces.live.com/
http://twitter.com/ThakurVinay
May 5, 2009 at 12:46 pm
It will work but the root cause should be investigated. It usually leads to inefficient queries and unnecessary large DML activities.
* Noel
May 6, 2009 at 8:23 pm
noeld (5/5/2009)
It will work but the root cause should be investigated. It usually leads to inefficient queries and unnecessary large DML activities.
ok thx i will try it ..thx for teaching me about it:-D
May 6, 2009 at 8:25 pm
Vinay (5/5/2009)
goto agent profile->Create new profile with:
log reader -QueryTimeout =10000...
re-run the log reader this will work.
HTH.
Thanx.
thx ya.. i will try it out izzit tis get my log reader work....thx 😛
May 28, 2009 at 2:02 am
Hi all. I got the same error. I created a custom agent profile for Log Reader Agents, I stopped Snapshot and Log Reader agents and started them again.
Any help is appreciated
Diego
May 28, 2009 at 8:31 am
why you started snapshot agent....
What error are you getting?
what is failing in your replication, is sql server is working good. Disk drives are accessable.
Just try to restart the log reader again?if not create a new profile for log reader with query timeout high value...(high it depends on the transactions).
more info will help to resolve better
Cheers.
Vin.
Thanx.
Vinay
http://rdbmsexperts.com/Blogs/
http://vinay-thakur.spaces.live.com/
http://twitter.com/ThakurVinay
May 19, 2010 at 3:54 am
Hi, Vin .... sorry for the delay but I forgot this post ....
The problem was solved!
Cheers
Diego
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply