Results 1 to 2 of 2

Thread: The process could not execute 'sp_replcmds' on [Server name]

  1. #1
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    301
    Rep Power
    6

    The process could not execute 'sp_replcmds' on [Server name]

    When I have my task set for the following and got the error

    “Prevent truncation of unread changes from TLOG” was set to “Start transactions in the database”
    (safeguardPolicy=RELY_ON_SQL_SERVER_REPLICATION_AG ENT;)

    Error:

    The process could not execute 'sp_replcmds' on [Server name]

  2. #2
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    301
    Rep Power
    6
    The problem is in the level of SQL server replication, which Replicate doesn't interact with.
    In this mode (truncation safeguard, not using sp_repldone), Replicate will not interact with MS-Replication, besides the initial creation of publication.

    Assuming that the database is still functioning, and you are able to run changes on it, and read data from it.
    However, Replication process is having a problem.
    The main impact you will see is that Active Log may not truncate and keep growing, but as long as it has disk space, the database will function properly.

    ====


    Replicate activates MS-Replication on the source database that it is replicating, but doesn't directly interfere with Replication besides
    Creating a publication on the source database when it first runs.


    We do read the transaction log directly using MS-SQL functions like fn_dblog but we do require replication to be on the source database, so the transaction log will contain the information that we need for CDC, and is not written to the log without replication set on it.


    Stopping The Log reader agent will not help, as if you stop the log reader agent , the Active Log will not be truncated. The log reader agent marks the Active logs parts that were replicated, so they can be truncated, so you should keep it running.

    ====


    the solution –
    The specified LSN {00000000:00000000:0000} for repldone log scan occurs before the current start of replication in the log {00001123:0000edab:0003}. (Source: MSSQLServer, Error number: 18768)


    We researched this error, and there a few articles discussing it. For example:


    https://www.microsoft.com/technet/su...rver&LCID=1033


    https://social.msdn.microsoft.com/Fo...sqlreplication


    Help replication issue..The process could not execute 'sp_repldone/sp_replcounters


    The articles suggest that the error is caused by some lost of sync between the SQL server publisher and the distributer.
    The articles suggest a number of ways to handle the issue, including try to reinitiate the subscription, or to try to run sp_replrestart to restart the replication.

Posting Permissions

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