Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

The specified LSN for repldone log scan occurs before the current start of replication in the log Expand / Collapse
Author
Message
Posted Tuesday, August 31, 2004 9:57 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, November 19, 2013 9:57 AM
Points: 2, Visits: 102

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




Post #134709
Posted Friday, September 3, 2004 8:00 AM
SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, May 18, 2007 3:36 PM
Points: 10,039, Visits: 1
No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!
Post #135253
Posted Thursday, September 16, 2004 7:08 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, October 7, 2013 6:12 PM
Points: 135, Visits: 87
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.
Post #137504
Posted Friday, September 17, 2004 7:40 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, November 19, 2013 9:57 AM
Points: 2, Visits: 102

Thanks Bimal.

That is what I ended up having to do.

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




Post #137570
Posted Wednesday, July 27, 2005 9:01 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, August 30, 2007 9:12 PM
Points: 28, Visits: 1
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
Post #204953
Posted Thursday, July 28, 2005 4:46 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 14, 2014 7:35 AM
Points: 278, Visits: 223

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

Post #205223
Posted Monday, March 26, 2007 9:21 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, April 25, 2007 8:46 AM
Points: 1, Visits: 1

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

sp_replrestart

Post #353885
Posted Tuesday, June 12, 2007 12:06 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, June 12, 2007 12:03 PM
Points: 1, Visits: 1

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

This will reinitialise the LogReader

Post #373197
Posted Tuesday, February 5, 2008 4:50 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 9:38 AM
Points: 48, Visits: 423
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!
Post #451544
Posted Friday, December 5, 2008 6:04 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, June 20, 2009 10:53 AM
Points: 1, Visits: 9
Great advice! It worked like a charm.

Thxs,

G.
Post #614435
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse