Post reply

replication not re-initializing

  • May 12, 2005 at 12:46 am

    #86534

    My merge replication was running fine but for somehow I need to mark it as re-initialize, I did it but its being 4 days now, that replication's reinitiallizing process is not get completed. I have stop and restart the agent many times.

    It first run Tables.SCH files then it says that copy data to merge_content... but after some interval it respond with failure, but when I do right-click on it to stop / start it again, it showing its status running.

    What can I do to complete this process?

    Thanks & Regards

    - Govind

  • May 13, 2005 at 8:13 am

    #558728

    try the following: re-create and apply a new snapshot

    what is the error that you are getting on the failure, what is the size of the table ??

    SQLDraggon -->> Good luck

    Don't count what you do, do what counts.

    SQL Draggon

  • May 13, 2005 at 10:29 pm

    #558886

    I've 1.5 GB of MDF file. But now I'm getting an 'Error Detail' that is

    1) The process could not bulk copy into table '"dbo"."MSmerge_contents"'.

    2) Cannot insert duplicate key row in object 'MSmerge_contents' with unique index 'uc1SycContents'.

    3) Function sequence error

    I think I have to clean-up the ms_merge_contents & tombstone table

    then re-initialize it again.

    any guru's advice?

     

    - Govind

     

  • May 17, 2005 at 10:37 pm

    #559453

    I was getting the same error, after recreation of subscription. So I create a new database on my subscription then again subscribe it, after that I'm able to build it

    - Govind

     

  • May 18, 2005 at 8:05 am

    #559584

    It appears that your system tables (Msmerge_contents, MSmerge_tombstone and Msmerge_genhistory) have grown enogh to give you grief. As you want to reinitialize, here is what you need to do.

    1. Alter your publication status by running this command.

    EXEC dbo.sp_changemergepublication @publication = <pub_name>, @property = 'status', @value = 'inactive'

    2. EXEC dbo.sp_mergecleanupmetadata @publication = <pub_name>

    3. Activate your publication.

    EXEC dbo.sp_changemergepublication @publication = <pub_name>, @property = 'status', @value = 'active'

    4. Run your snapshot.

    Do you reindex/update your system tables?  You may have tyo do them as part of your maintenance plan, once a week.

  • May 19, 2005 at 11:16 pm

    #560099

    Thanks Fellow, but even MS also suggests that (inactive, clean-up metadata, active). I did this but failed again. I had tried everything that I found as solution. But now its working smoothly on the new Database, why i create new Database is that I don't want to re-create my publication's articles again.

    Thanks

    - Govind Bhavan

     

  • August 6, 2007 at 9:52 am

    #724895

    Hi I was gettting the same problem, this worked for me

    thanks

     

    Dave

  • September 2, 2007 at 6:26 pm

    #730950

    I also had this problem and then found that the collation was set wrong for the subscribers database which I had created with a script.  As soon as I dropped the database and re-created with correct collation it worked.

     

    Cheers

     

    Carl

  • July 16, 2011 at 7:33 am

    #1353842

    Thanks a lot,

    that helpeed.

Viewing 9 posts - 1 through 8 (of 8 total)

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