Quantcast
Channel: SQL Server Replication forum
Viewing all articles
Browse latest Browse all 4054

Error: "The specified LSN {000...000} for repldone log scan occurs before the current start of replication in the log"

$
0
0

All,

We have a replication solution set up for one of our OLTP databases and we use the initialize from backup option to initialize the subscription.  We performed an upgrade of our OLTP software over the weekend and the admin who did it is not noticing this error in Replication Monitor:

  • The process could not execute 'sp_repldone/sp_replcounters' on ...
  • The specified LSN {00000000:00000000:0000} for repldone log scan occurs before the current start of replication in the log {00029ddb:00001bb3:010a}.
  • The process coult not set the last distributed transaction.

What is interesting is the LSN number for the log scan:  {00000000:00000000:0000}.  This would be the very beginning of the log file.  Is anyone familiar with the 'initalize from backup' option and this error (i.e., where it points to the beginning of the log)?

Also, we want to ensure the data in our subscriber is properly synched with what's in the publisher.  Is there a way to do this without having to go through the whole process of recreating the sucscription (which takes several hours)?

Also,

When I run sp_replshowcmds on the publisher I get the following:

xact_seqno originator_srvname originator_db article_id type partial_command hashkey originator_publication_id originator_db_version originator_lsn command command_id
0x00029DDB00001FE60004   0 0 0 0 NULL NULL NULL  1

And when I run DBCC OPENTRAN on the publisher this is what it tells me about replication:

Replicated Transaction Information:

        Oldest distributed LSN     : (171483:7091:266)

        Oldest non-distributed LSN : (171483:8166:1)

Any help is greatly appreciated!



Viewing all articles
Browse latest Browse all 4054

Trending Articles