Distribution Agent set with Continuous parameter stops with "Completed Successfully"

Unanswered Distribution Agent set with Continuous parameter stops with "Completed Successfully"

  • 11 เมษายน 2555 18:03
     
     

    I have created custom profile for both Log Reader and Distribution Agent.  Added the  –MaxCmdsInTran parameter at the command line for the Log Reader and now in replication monitor is displays as "Not Running".

    My distribution job runs for about an hour then shuts down with "The replication agent completed successfully. See the previous job step history message or Replication Monitor for more information.  The step succeeded." even though the Continuous parameter is supplied.

    Replication Distributor

    -Subscriber [DEV2\DBC] -SubscriberDB [DevDB2] -Publisher [DEV4\DBF] -Distributor [DEV4\DBF] -DistributorSecurityMode 1 -Publication [Large_Data_Testing] -PublisherDB [DevDB3] -Continuous

    Any idea what could be causing this?

ตอบทั้งหมด

  • 12 เมษายน 2555 2:22
    ผู้ดูแล
     
     

    Hi Geek_Mon,

    It seems that something wrong with the Log Reader Agent. Could you please look into the agent history for more information? Add to that, you can make use of –output commend to capture detail messages about agent failure for troubleshooting, please see: Replication Failed with Log Reader Agent Failed to Construct Command.

    For your reference: Replication Failed with Log Reader Agent Failed to Construct Command.

    TechNet Subscriber Support
    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Stephanie Lv

    TechNet Community Support

    • ทำเครื่องหมายเป็นคำตอบโดย Stephanie LvModerator 19 เมษายน 2555 7:56
    • ยกเลิกการทำเครื่องหมายเป็นคำตอบโดย Geek_Mom 20 เมษายน 2555 20:48
    •  
  • 20 เมษายน 2555 21:44
     
     

    No errors in the Log Reader history. I have not been able to capture it occuring since I have turned on the Output parameter.  The logreader is consistently very busy, so we see the scanning transaction log message frequently.

    However, on the Distribution agent, there appears to have been a communications failure.  The distribution agent re-tried, was successful in distributing transactions, then shut down. 

    1. "Cannot open database xxx"
    2. "Replication Agent encountered an error and is set to restart"
    3. "The replication agent has been successfully started."2012-04-19 20:29:26.037
      ************************ STATISTICS SINCE AGENT STARTED ***********************
      Total Run Time (ms) : 170777594  Total Work Time  : 10483451
      Total Num Trans     : 134  Num Trans/Sec    : 0.01
      Total Num Cmds      : 209914  Num Cmds/Sec     : 20.02
      Total Idle Time     : 159675217

    Writer Thread Stats
      Total Number of Retries   : 0
      Time Spent on Exec        : 10475432
      Time Spent on Commits (ms): 142329  Commits/Sec         : 3.03
      Time to Apply Cmds (ms)   : 10483451  Cmds/Sec            : 20.02
      Time Cmd Queue Empty (ms) : 624221  Empty Q Waits > 10ms: 258
      Total Time Request Blk(ms): 160299438
      P2P Work Time (ms)        : 0  P2P Cmds Skipped    : 0

    Reader Thread Stats
      Calls to Retrieve Cmds    : 31960
      Time to Retrieve Cmds (ms): 296005  Cmds/Sec            : 709.16
      Time Cmd Queue Full (ms)  : 10457332  Full Q Waits > 10ms : 1112

    2012-04-19 20:29:46.047 No replicated transactions are available.
    ... More Transactions
    2012-04-19 20:33:22.433 30 transaction(s) with 30 command(s) were delivered.
    2012-04-19 20:33:27.473 ************************ STATISTICS SINCE AGENT STARTED ***********************
    Total Run Time (ms) : 171019031  Total Work Time  : 10484529
    Total Num Trans     : 1000  Num Trans/Sec    : 0.10
    Total Num Cmds      : 210780  Num Cmds/Sec     : 20.10
    Total Idle Time     : 159915217

    Writer Thread Stats
      Total Number of Retries   : 0
      Time Spent on Exec        : 10476136
      Time Spent on Commits (ms): 142500  Commits/Sec         : 3.04
      Time to Apply Cmds (ms)   : 10484529  Cmds/Sec            : 20.10
      Time Cmd Queue Empty (ms) : 624596  Empty Q Waits > 10ms: 283
      Total Time Request Blk(ms): 160539813
      P2P Work Time (ms)        : 0  P2P Cmds Skipped    : 0

    Reader Thread Stats
      Calls to Retrieve Cmds    : 32031
      Time to Retrieve Cmds (ms): 296208  Cmds/Sec            : 711.59
      Time Cmd Queue Full (ms)  : 10457332  Full Q Waits > 10ms : 1112

    4. The replication agent completed successfully. See the previous job step history message or Replication Monitor for more information.  The step succeeded.

    And the job stops as completed successfully.  Even with the continuous parameter specified.