Replication Issue.

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » Replication Issue.

Replication Issue.

Rate Topic

Display Mode

Topic Options

Author

Message

Ranzz

Posted Saturday, September 15, 2012 12:28 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, May 09, 2013 11:26 AM
Points: 138, Visits: 509

When I try to run sanpshot job is also failing.

When I replication monitor, I see below error. Help needed.

Error messages:
The process could not execute 'sp_repldone/sp_replcounters' on 'Server_name'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
The log scan number (690:13675:299) passed to log scan in database 'DB_Name' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. (Source: MSSQLServer, Error number: 9003)
Get help: http://help/9003
The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
Get help: http://help/MSSQL_REPL22017
The process could not execute 'sp_repldone/sp_replcounters' on 'USSTLPMPINFDB63'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037

Post #1359833

MysteryJimbo

Posted Sunday, September 16, 2012 2:10 AM

Ten Centuries

Group: General Forum Members
Last Login: Monday, May 06, 2013 8:14 AM
Points: 1,125, Visits: 14,510

Danzz (9/15/2012)

The log scan number (690:13675:299) passed to log scan in database 'DB_Name' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. (Source: MSSQLServer, Error number: 9003)

I should start by running checkdb on the published database. If that reports no errors you are going to have to set up the publication again. It seems the log reader cannot find a pointer in the log file to get any additional transactions (post BCP data export).

Post #1359869

prettsons

Posted Wednesday, September 19, 2012 9:51 PM

SSC Journeyman

Group: General Forum Members
Last Login: Thursday, May 16, 2013 12:17 AM
Points: 99, Visits: 1,023

This error occurs due to two causes:

1. The last LSN in Transaction Log is less than what the LSN Log Reader is trying to find. An old backup may have been restored on top of Published Database. After the restore, the new Transaction Log doesn't contain the data now distributor & subscriber(s) have.
2. Database corruption.

You should follow these steps to fix the error:

1. Ensure database consistency by running DBCC CHECKDB on the database.
2. If an old backup was restored on top of published database then use sp_replrestart

If going back to the most recent transaction log backup is not an option then execute sp_replrestart on publisher in published database. This stored procedure is used when the highest log sequence number (LSN) value at the Distributor does match the highest LSN value at the Publisher.

This stored procedure will insert compensating LSNs (No Operation) in the publisher database log file till one the compensating LSN becomes more than the highest distributed LSN in distribution database for this published database. After this it inserts this new high LSN in the msrepl_transactions table in the distribution database and executes sp_repldone on published database to update the internal structures to mark a new starting point for log reader agent.

Ensure that the log reader agent is stopped and there is no incoming transactions on the published database, when this SP is executed.

3. Since transactions may have been lost, we recommend to reinitialize the subscriber(s) and/or recreate publication/subscription(s). For large databases consider using “Initialize from Backup” as discussed in SQL Book Online.

Ref: http://blogs.msdn.com/b/repltalk/archive/2010/02/19/the-process-could-not-execute-sp-repldone-sp-replcounters.aspx

SQL Database Recovery Expert Smile

Post #1361717

« Prev Topic | Next Topic »

Permissions