Post reply

sp_repldone

  • December 31, 2014 at 2:41 am

    #299811

    I have setup CDC for a database 'ABC' .Database 'ABC' is in simple recovery model.

    log file getting full always ,it shows 'REPLICATION' if i check the 'log_reuse_wait_desc' FROM SYS.DATABASES for this database 'ABC' .

    is it fine to run the below command to clear the log?

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

    is there any affect to existing CDC ?

  • December 31, 2014 at 2:49 am

    #1767146

    Yes, that will affect CDC. No, it's not the way to fix the problem

    Check that all the CDC jobs are running correctly and succeeding.

    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 31, 2014 at 2:59 am

    #1767148

    CDC jobs are running fine.

    pls suggest how to resolve this issue ?

  • December 31, 2014 at 3:15 am

    #1767151

    You sure you don't also have transactional replication set up?

    Are all the CDC jobs running properly? There's more than one and I can't recall which is the one that reads the 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

  • December 31, 2014 at 3:22 am

    #1767152

    yes, i don't have transactional replication set up.

    yes ,all the CDC jobs are running properly.

  • December 31, 2014 at 3:28 am

    #1767153

    There's only two ways you get this log wait

    1 - Transactional replication that's not properly set up/broken/not running

    2 - CDC jobs that aren't running/aren't succeeding.

    Nothing else will cause a replication log wait

    Try creating a transactional replication publication, publishing a single table and then dropping publication. That will fix things if there's some broken remnants of replication. If it doesn't, then you'll need to dig deeper into the CDC.

    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 6 posts - 1 through 5 (of 5 total)

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