dcsimg
Results 1 to 2 of 2

Thread: retention-based meta data cleanup

  1. #1
    Join Date
    Apr 2005
    Posts
    1

    retention-based meta data cleanup

    Hi

    I am running a couple of sql 2000 SP3a servers with merge and snapshot replication. One server acting as publisher and distributor and the rest subscribers. On one of the server I have got the error below and have tried most of the suggestions by msdn. This server has not crashed ever before or any hardware problems. It has been running for a couple of months and no problems. This has not happened no any of the other servers. Any suggestions would be greatly appreciated as the only resolution I have left is to bring up a new instance, setup replication and see if this would resolve the issue. Stopping and starting of agents don't work.


    [4/18/2005 11:59:20 AM]BRAAMPDC1\ICAS2000.HO_Master: {call sp_MSgetversion }
    [4/18/2005 11:59:20 AM]BRAAMPDC1\ICAS2000.distribution: {call sp_MShelp_subscriber_info (N'BRAAMPDC1\ICAS2000', N'EASTSRV3')}
    Connecting to Subscriber 'EASTSRV3.ICASData'

    Server: EASTSRV3
    DBMS: Microsoft SQL Server
    Version: 08.00.0760
    user name: dbo
    API conformance: 2
    SQL conformance: 1
    transaction capable: 2
    read only: N
    identifier quote char: "
    non_nullable_columns: 1
    owner usage: 31
    max table name len: 128
    max column name len: 128
    need long data len: Y
    max columns in table: 1024
    max columns in index: 16
    max char literal len: 524288
    max statement len: 524288
    max row size: 524288

    [4/18/2005 11:59:27 AM]EASTSRV3.ICASData: {call sp_MSgetversion }
    Percent Complete: 2
    Connecting to Subscriber 'EASTSRV3'
    Percent Complete: 3
    Retrieving publication information
    Percent Complete: 4
    Retrieving subscription information
    Percent Complete: 4
    The merge process is cleaning up meta data in database 'HO_Master'.
    Percent Complete: 4
    The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
    Percent Complete: 4
    The merge process is cleaning up meta data in database 'ICASData'.
    The merge process could not perform retention-based meta data cleanup in database 'ICASData'.
    Percent Complete: 0
    The merge process could not perform retention-based meta data cleanup in database 'ICASData'.
    Percent Complete: 0
    Category:NULL
    Source: Merge Replication Provider
    Number: -2147199467
    Message: The merge process could not perform retention-based meta data cleanup in database 'ICASData'.
    Percent Complete: 0
    Category:COMMAND
    Source: Failed Command
    Number: 0
    Message: {call sp_mergemetadataretentioncleanup(?, ?, ?)}
    Percent Complete: 0
    Category:SQLSERVER
    Source: EASTSRV3
    Number: 11
    Message: General network error. Check your network documentation.

  2. #2
    Join Date
    Feb 2003
    Posts
    1,048
    Errors like "retention-based meta data cleanup" errors are generally caused by network errors. It can be something as simple as extremely high network traffic or a faulty Nic card.

    We used to get quite a bit of these errors because we were using load balanced Nic cards on our SQL Servers .... which is problematic at times. We switched to using single heavy duty Nic cards and the problem was pretty much resolved.

    If this does happen now, generally it will clear up if I stop the merge agent, wait about 30 seconds, and then start it up again. If that doesn't work, try rebooting.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •