none
Replication: There is this merge replication which often shows genstatus with value 4 RRS feed

  • Question

  • Replication: There is this merge replication which often shows genstatus with value 4. How to address it and minimize reoccurrence ?
    Saturday, August 24, 2019 2:16 AM

All replies

  • Hi Tulip2019,

     

    What is the version of sql server are you using? Here is the similar issue for your reference : https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ab17199f-56c5-4431-8a7c-dbf33f969475/why-does-my-genstatus-4?forum=sqlreplication

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, August 26, 2019 7:19 AM
  • GenStatus of 4 means an error has occurred and the generation will be picked up with the next sync. The documentation says "generation came from elsewhere and was inserted by the synchronization process. The generation is open and possibly an interrupted generation."

    Basically what happens after a sync is occurred all changes are assigned an new generation and the genstatus is set to 0. When the sync starts it is set to 1 for that generation and all subsequent changes have a new generation.  

    A generation of 4 basically means that the generation is out of sequence and merge replication does not really know what to do with it, so it reprocesses the rows associated with that generation and the current generation in the next sync.

    Monday, August 26, 2019 1:47 PM
    Moderator
  • The version is SQL 2012 with SP2.
    Wednesday, September 4, 2019 4:47 AM
  • But, we have seen these type of genstatus coming back when we reinitialize the sync. What causes this error/interruption? There is mismatch in the data on publisher and subscriber.
    Wednesday, September 4, 2019 4:53 AM