The specified LSN for repldone log scan occurs before the current start of replication in the log

  • jshaver

    SSC Enthusiast

    Points: 142

    Anybody know how to clean this up on a Log Reader Agent:

    The specified LSN (0000f7b8:000000f6:0001) for repldone log scan occurs before the current start of replication in the log (00014d5f:00000814:0004).

    Thanks,

    Jeff

  • Bimal Fernando

    SSCommitted

    Points: 1945

    I also go the same error after our ditributor (subscriber too) machine got crashed with a blue screen. I just had to re create the publication and the subscription to fix the problem.

  • jshaver

    SSC Enthusiast

    Points: 142

    Thanks Bimal.

    That is what I ended up having to do.

    I also ran sp_repldone with @reset = 1 to help clean things up.

  • Borik

    SSC Eights!

    Points: 908

    I got the same problme and running “sp_repldone with @reset = 1” didn’t help

    now i get

    Another log reader is replicating the database.

    (Source: TESQLSRV3 (Data source); Error number: 18752)

    ———————————————————————————–

    The process could not set the last distributed transaction.

    (Source: TESQLSRV3-TE_CVIO_NYC-3 (Agent); Error number: 22017)

    ———————————————————————————–

    any further help would be appreceteve…

    don’t want to rebuild 9Gig replication

    Borik

  • Hilary Cotter

    SSCommitted

    Points: 1856

    You will have to manually fix the replication metadata tables. However the quick and dirty way to fix this is to

    1) drop your subscription

    2) recreate your subscription with a no-sync subscription

    3) use the continue on data consistency errors profiler

    4) do a validation to determine which tables are out of sync

    5) manually fix these tables

     

    Hilary Cotter

    Looking for a SQL Server replication book?

    http://www.nwsu.com/0974973602.html

    Looking for a FAQ on Indexing Services/SQL FTS

    http://www.indexserverfaq.com

  • Stephen Cassady

    Valued Member

    Points: 73

    Don’t rebuild and drop and all that, just use

    sp_replrestart

  • jfl

    Valued Member

    Points: 73

    In order to restart the Logreader, use SQL Suery analyser, select the replicated database and execute : sp_replrestart

    This will reinitialise the LogReader

  • neil-560592

    Default port

    Points: 1420

    If you are getting the message “Another log reader is replicating the database” after you have been trying to mark transactions as replicated, a possible cause is that you have been using query analyzer to try running sp_repldone AND that you have left this query window open after going on to try other things. I am of the opinion that SQL Server then sees this connection as being a logreader (because of course logreader calls sp_repldone as well).

    So try closing query analyzer and see whether this message goes away. It did with me!

  • gloret

    Valued Member

    Points: 71

    Great advice! It worked like a charm.

    Thxs,

    G.

  • Mister Sachmo

    SSCommitted

    Points: 1618

    Stephen Cassady (3/26/2007)


    Don't rebuild and drop and all that, just use

    sp_replrestart

    This worked for me. Ran this on the publisher database, and the logreader ran fine. I’m going to read up some more on replrestart.

  • Lars Søe Mikkelsen

    SSCommitted

    Points: 1602

    Stephen Cassady (3/26/2007)


    Don't rebuild and drop and all that, just use

    sp_replrestart

    I had the same problem and this fixed it for me. Thanks alot!

    (I ran it on the database being replicated.)

  • Matt Slocum

    Ten Centuries

    Points: 1357

    I know I’m reviving an old thread, but I just ran into this issue the other day and I decided to take the time to blog on the topic of recovering from this situation.

    Check it out if you’re interested: http://mattslocumsql.blogspot.com/2012/04/replication-troubleshooting-how-to-deal.html

Viewing 12 posts - 1 through 12 (of 12 total)

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