Post reply

Strange Replication issue - trying to find root cause

  • November 18, 2015 at 11:35 am

    #309702

    Hi All,

    We encountered a strange replication issue. Our client told us that the subscriber database is not up to date. Thus we checked to verify if there is any latency. We found about 3 hour latency. We waited for some time to see if we can find any improvement but it didn't change. Thus we restarted logreader replication job and replication came back to sync in about 5 minutes.

    We are trying to find root cause of this issue. As I mentioned the resolution was just to restart replication job and it came back to sync. But not sure why it didn't sync itself because replication job was already running.

    Did you encounter this similar issue? If yes what was the root cause?

    Thanks.

  • November 19, 2015 at 5:34 am

    #1840946

    You may never find an issue to this answer. Sometimes Replication just stops.

    The first places to check, though, would be the error logs (for any weird warnings or errors) and to check around for network issues around the time that Replication stopped working. Sometimes a network outage can kill a connection at one server, but make another server still think the connection is open.

    Then keep an eye on Rep and, if you see the issue again, note all the common denominators between the last time and "this" time.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • November 19, 2015 at 7:29 am

    #1840980

    This can be the issue with network. We have experienced the same issue.

  • November 19, 2015 at 7:38 am

    #1840991

    Thanks, will keep digging..

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply