HELP>>> I am getting desperate
we recently had a failure which ended up wrecking my replication. The basic layout is from a source server -> Distribution Server then out to several other servers. Long story short the distribution database had to be moved to a new drive and I am now getting the following error message
we recently had a failure which ended up wrecking my replication. The basic layout is from a source server -> Distribution Server then out to several other servers. Long story short the distribution database had to be moved to a new drive and I am now getting the following error message
The specified LSN (0003d4f0:0000721e:001b) for repldone log scan occurs before the current start of replication in the log (0003d63a:00002803:0001).
(Source: fsdpdcis (Data source); Error number: 18768)
---------------------------------------------------------------------------------------------------------------
The process could not set the last distributed transaction.
(Source: fsdpdcis-DPDDATA-1 (Agent); Error number: 22017)
(Source: fsdpdcis (Data source); Error number: 18768)
---------------------------------------------------------------------------------------------------------------
The process could not set the last distributed transaction.
(Source: fsdpdcis-DPDDATA-1 (Agent); Error number: 22017)
I have reinitialized all subscriptions on the fsdpdcis server and run subscription validation (with no response). The data did re-load during the reinitialization but does not seem to be getting updated. This is driving me crazy and I am desperate. Any suggestions would be greatly appreciated. I have search MS knowledge base with no results and BOL has not been any help so far.
Thanks
Steve
Log Reader Agent Failure
n00b_5876
Hi Steve,
Looks like your publication and distribution servers are out of step, which is causing SQL Server log reader to "think" transaction log order is incorrect. If you didn't backup your databases and disable agent job with emphasis on distribution database, this is more likely to have caused your problem.
Action
Drop publications and subscribers and re-create, starting with smallest database first. Once this is done, then re-enlist subscribers.
If you have any additional questions, please contact me at phillipalbertcox@hotmail.com
shweta13
Hey,
Excellent result and don't hesitate if you need any additional help, but just give me a day or so to reply.
Cheers
psykik
Phillip,
I greatly appreciate your reponse. I was able to find a referense to a stored procedure(sp_replrestart) which effectively brought the LUN back into sync by replacing the missing time stamps with "no operation" entries. I then was able to reinitialize the subscriptions and now all is operating normally.
Thanks for the reply. I am fairly new to SQL and need all the help I can get.