Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
govthamb
Starting Member
27 Posts |
 Posted - 2013-01-31 : 08:10:03
|
| We have an issue in Transactional Replication which is configured in our environment.As part of compliance we have applied OS level patches and rebooted the SQL server, post reboot all SQL services and Log Reader agents etc are back to running state.Based on the replication monitor observed that articles which are in replication are not updated from Publisher to Subscriber, checked and found that LOG reader agent is in running status only, no specific error found in replication monitor, job history, event viewer etc.. Restarted the Log Reader Agent and automatically replication is in sync again.Client wants to know RCA, why replication out of sync even though Jobs & Log reader agent is running fine.Need your help in this regard. |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-01-31 : 09:57:50
|
| There is an issue with Replication Monitor, where after a reboot it misreports undistributed commands (shows a number greater than 0 when in fact there are none). Restarting the distribution agent solves it. If you have many publications, easier to just restart SQL Agent on the distributor.So probably, you were in synch the whole time, but ReplMon reported otherwise. |
 |
|
|
govthamb
Starting Member
27 Posts |
Posted - 2013-01-31 : 11:30:30
|
| Thanks Russell for the information, is there any MS article which supports this issue with Replication Monitor, so that we can provide the same info to our client as well. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-01-31 : 14:30:45
|
| Not that I've seen. I know this from years of experience. ReplMon is quick and convenient, but should not be relied upon as your only tool for replication monitoring.Anyone administering replication should start here |
|
|
|
govthamb
Starting Member
27 Posts |
Posted - 2013-02-01 : 08:18:56
|
| Thanks Russel for the info. We have observed several times a scenario where replication monitor is showing unditributed commands as 0, but when we check manually, records in publisher and subscriber are not matching. Again we need to restart the Log reader agent to make the data in sync. Is this onle of the bug in replication monitor or are we missing anything from our end.Please suggest. |
|
|
|
|
|
|
|
|
Replication went to out of sync