June 27, 2008 at 4:18 am
Hi,
My database has 2 replication in 2 other servers.
Yesterday, I recognized that I had some problems when inputed data in database. My data was wrong.
I restored the database from a backup some days before (before I inputed wrong data).
But, then, I've been having this error when trying to synchronize data between those databases:
The LSN (122977:1181:1) passed to log scan in database 'Database_Name' is invalid.
(Source: SERVERDATA (Data source); Error number: 9003)
---------------------------------------------------------------------------------------------------------------
The process could not set the last distributed transaction.
(Source: SERVERDATA-DatabaseName-8 (Agent); Error number: 22017)
---------------------------------------------------------------------------------------------------------------
I use SQL Server 2000.
Could anyone help me please!
Thanks so much!
June 27, 2008 at 12:53 pm
You've taken the publication database back in time and so the subscribers are further ahead. The Log Reader Agent is confused because suddenly the log records it is reading are chronologically before the last ones it read from before you restored from the backup.
You basically need to re-setup replication so everything gets re-synched.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
June 28, 2008 at 1:04 am
Dear Mr Paul Randal,
Thank you for your anwser!
I wonder if there's a way we can resolve that problem without re-setup replications. Because, one of 2 replications is in another country (It's in Japan, and I'm in Vietnam), it's difficult for me to re-setup that replication.
I'm trying to re-create the publications, but.....
Could you help me please!
Mai Huong
June 28, 2008 at 1:09 am
Nope - as I said before, you need to re-setup replication as you've completely broken it by taking the publication database back in time. No-one will tell you any different.
Thanks
PS I'm offline now until July 8th.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
July 4, 2008 at 7:58 pm
Dear Mr Paul Randal,
I've already resolved this error with your help.
Thank you very much!
Mai Huong.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply