January 15, 2004 at 1:36 pm
Hello,
I have a replicated Database which is used for reporting purposes. The replication fails frequently. Normally its the logreader that fails and stops with error 'The process could not execute 'sp_replcmds' on Server1'. If I manually try and restart the log reader, it fails with the same error very soon. so we resort to re-initializing. But due to the volume of data, it takes a long time and now its a real pain for the business.
The distributor and publisher run without any issues.
Is there anything that could be done to avoid such failures? if It happens again, is there any way I could restore the repl without reinitializing it?
Also the below error is something I found from event_log.
17066 :
SQL Server Assertion: File: <logscan.cpp>, line=1889
Failed Assertion = 'startLSN >= m_curLSN'.
Any help please?
Regards
January 16, 2004 at 9:21 am
I think the reason of the failure is because some transaction did not get replciated correctly. Did you try sp_repldone ? Is this on SQL 7 ?
January 16, 2004 at 12:02 pm
Thanks for the reply. This is on SQL2000. I have tried sp_repldone. No use.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply