locked
Regarding Merge Replication? RRS feed

  • Question

  • Few weeks back i configure the merge replication.after that the customer can't modified the particular row in the particular table on a publisher database.I checked the table their is no lock (row) and their is no blocking.The replication runs fine.

    Now customer said i faced this problem randomly in a table.and the customer get the error message (ODBC time out error).Is their any suggestions except to increase the ODBC time?

    What is the problem and how can i resolve the that issue.(Before run the Profiler)

    Tuesday, July 19, 2011 5:51 AM

Answers

  • Hi rupc,

    I think you may need to increase the QueryTimeOut value.

    The first step in resolving this issue is to increase the time-out setting for the Merge Agent. You can set this time-out by specifying the -QueryTimeOut argument when starting the Replication Merge Agent.

    In SQL Server Enterprise Manager, expand Replication Monitor and the Agent folder.

    1. Expand the folder for the Merge Agent.

    2. Right-click the agent, and then click Agent Properties.

    3. In the Agent Properties dialog box, click the Steps tab.

    4. Select the Run Agent step, and then click Edit.

    5. In the Command text box, add -QueryTimeOut to the end of the command. The command line should look like:
      -Publisher [SamplePub] -PublisherDB [SamplePubDB] -Publication [SamplePublication] 
      -Subscriber [SampleSub] -SubscriberDB [SampleSubDB] -Distributor [SampleDist] 
      -DistributorSecurityMode 1 –QueryTimeOut
      

       

      Note  Line breaks in the previous example are added to improve readability. In the Command text box, parameters must be provided on a single line.

    6. To save changes and close, click OK.

    Regards,

    Vishal.


    Regards, Vishal Srivastava
    Tuesday, July 19, 2011 3:22 PM

All replies

  • When you face the issue during the row insertion run select waittime,waittype,blocked on the SPID and post the output ...
    Abhay Chaudhary OCP 9i, MCTS/MCITP (SQL Server 2005, 2008, 2005 BI) ms-abhay.blogspot.com/
    Tuesday, July 19, 2011 7:09 AM
  • There might be problem with Triggers ...please check creted triggeres for update or insert while configuriong Replication .
    Kuldeep
    Tuesday, July 19, 2011 8:26 AM
  • Hi rupc,

    I think you may need to increase the QueryTimeOut value.

    The first step in resolving this issue is to increase the time-out setting for the Merge Agent. You can set this time-out by specifying the -QueryTimeOut argument when starting the Replication Merge Agent.

    In SQL Server Enterprise Manager, expand Replication Monitor and the Agent folder.

    1. Expand the folder for the Merge Agent.

    2. Right-click the agent, and then click Agent Properties.

    3. In the Agent Properties dialog box, click the Steps tab.

    4. Select the Run Agent step, and then click Edit.

    5. In the Command text box, add -QueryTimeOut to the end of the command. The command line should look like:
      -Publisher [SamplePub] -PublisherDB [SamplePubDB] -Publication [SamplePublication] 
      -Subscriber [SampleSub] -SubscriberDB [SampleSubDB] -Distributor [SampleDist] 
      -DistributorSecurityMode 1 –QueryTimeOut
      

       

      Note  Line breaks in the previous example are added to improve readability. In the Command text box, parameters must be provided on a single line.

    6. To save changes and close, click OK.

    Regards,

    Vishal.


    Regards, Vishal Srivastava
    Tuesday, July 19, 2011 3:22 PM