7 replies
by pvp
The last I knew, replication relies on log entries, somewhat like database restoration.
If you've been doing dump db, dump tran, dump tran...and miss a file in sequence, you cannot restore beyond the last sequence log entry that can be found.
I suspect that for your replication, you may have such a problem. The solution is probably to dump the publisher database, restore the subscriber database, then resume replication.
Also, the fact that truncate log won't, might indicate that you have a long-running or otherwise unterminated transaction in the log.
by xchen
by sonnysan
by xchen
greetings, try this, begin replication monitor; right click the distribution agent then click agent properties( allows you to view agent properties),click steps tab then double click run replication agent, cut the string from the command window and paste string into counsole window begining with distrib.exe and adding extra parameter -output, review output for indications of the problem. you can increase the amount of history logged and use this additional information to aquire a more detailed understanding of the actions and failures at each point of the process, set the historyverboselevel to it's highest setting in replication agent profile. hope this helps...
hbp
by xchen
by xchen
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending