June 24, 2006 at 12:30 pm
Here's my "lovely" situation.
We were switching over to new storage, and the network admin accidentally uninstalled SQL. The most recent system database backups were a day old. He reinstalled SQL, then restored the databases from the day before. All the user databases are fine, but replication is all screwed up, since the distribution db is missing all the logs from that day.
I figured I could "just" reinitialize all the subscriptions and start them from scratch, but the log reader won't start. The log reader job errors with:
The process could not execute sp_repldone sp_replcounters
So I thought maybe I should delete the the log reader, create a new publication to generate a new log reader, but that didn't work ....... Do I just delete everything somehow & start completely from scratch ???
What a mess !
June 24, 2006 at 3:04 pm
I found reference to the command "sp_replrestart" that seems to have helped get my log reader job going again (I had saved a script of the job so I could recreate it). At least I can now reinitialize my subscriptions and start them over.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply