Post reply

The transaction log for database 'xxxx' is full due to 'REPLICATION'."

  • December 4, 2014 at 2:11 am

    #295647

    getting below error most of the times .

    "Server was unable to process request. ---> The transaction log for database 'xxxx' is full due to 'REPLICATION'."

    i am doing below steps to clear the log everytime.

    1.EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0,@time = 0, @reset = 1

    2.checkpoint

    is the any permanent fix for this issue ?

  • December 4, 2014 at 2:25 am

    #1762623

    Hi,

    I think being in Full Recovery Mode and Not Taking Log Backups can be the reason for this. Try to take a log backup, or set your database recovery model to simple.

    Hope it helps.

    Cheers!

  • December 4, 2014 at 2:32 am

    #1762625

    Serlal (12/4/2014)

    I think being in Full Recovery Mode and Not Taking Log Backups can be the reason for this.

    No, it can not. Full recovery model and no log backups results in a log reuse wait desc of LOG BACKUP, not replication.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • December 4, 2014 at 2:33 am

    #1762626

    charipg (12/4/2014)

    "Server was unable to process request. ---> The transaction log for database 'xxxx' is full due to 'REPLICATION'."

    You have a transactional replication publication? Is the log reader agent not running?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • December 4, 2014 at 2:51 am

    #1762632

    db is in simple recovery model.

    no replication configured.

    But some CDC jobs are setup , is this the issue ?

  • December 4, 2014 at 2:53 am

    #1762633

    If CDC jobs are setup then you have to make sure that the t-log is not too large. Make sure you backup your log at regular intervals to make sure it is not growing too large

  • December 4, 2014 at 3:05 am

    #1762639

    charipg (12/4/2014)

    But some CDC jobs are setup , is this the issue ?

    If they're not running, yes.

    Do note, by running the repldone commands, you're invalidated the CDC stuff and lost changes. You probably need to disable and reconfigure it to get it working properly and providing a full change history.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • December 4, 2014 at 3:41 am

    #1762645

    CDC jobs are running fine..

    I disabled and reconfigured CDC stuff, still facing same issue frequently..

  • December 4, 2014 at 4:48 am

    #1762672

    Either you've also got transactional replication that's not running, or the CDC jobs are not all running properly. Only two ways you'll have long-lasting REPLICATION log reuse waits and a growing log

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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