General discussion

Locked

Restart SQL Server replication

By xchen ·
I stopped the replication of a SQL 7.0 database (100 MB) for a few months. Now I want to restart it. What I did were: deleted the existing publication and re-created a new one using "Create and Manage Publicaton…" menu. Recreation was successful, but replication could not continue due to an error during the "initializing…" phase of the "Log Reader". Err Msg: "The process could not initialize replication counters". It may be resulted from the size of the Transaction Log (1.3GB). Prior to stopping the replication, the size was 5 MB. Using "Truncate Transaction Log" did not decrease the size. I was trying to detach the database so that I could recreate a new database with the same name and start replication again, but the deletionfailed because the database is still marked as published. My goal is to restart the replication of the original or start a replication of a new database with the same name as the original. Please help.

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Restart SQL Server replication

by pVp In reply to Restart SQL Server replic ...

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.

Collapse -

Restart SQL Server replication

by xchen In reply to Restart SQL Server replic ...

Thanks. Your answer helped me partially.

Collapse -

Restart SQL Server replication

by sonnysan In reply to Restart SQL Server replic ...

Note catagory and error # in event viewer. Aquire a technet cd and type in catagory <error #> in search. Technet is the best source to troubleshoot error codes. Replication is one of the most technical issues of SQL. If technet doesn't help, thenext step is to call Microsoft at 1K/hour. Hope that helps.

Collapse -

Restart SQL Server replication

by xchen In reply to Restart SQL Server replic ...

Thanks for your efforts.

Collapse -

Restart SQL Server replication

by headbangerphil In reply to Restart SQL Server replic ...

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

Collapse -

Restart SQL Server replication

by xchen In reply to Restart SQL Server replic ...

Thanks. Your answer helped me partially.

Collapse -

Restart SQL Server replication

by xchen In reply to Restart SQL Server replic ...

This question was closed by the author

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums