 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Replication / October 2006log scan number
Yesterday, we attempted to add a new table to an existing publication. We then created the table on the subscriber and populated it manually. We expected that replication would then take over the data flow to this table. This morning, I found that the log reader had failed with the following: 2006-10-27 15:20:46.966 Status: 0, code: 9003, text: 'The log scan number (94570:3522:134) passed to log scan in database 'RawData' 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. '. 2006-10-27 15:20:46.966 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'CARZ0DB16\ARZSQL16'.'. Has anyone seen this error before? I've encountered this. Basically the log reader writes the last LSN read from the log into the distribution database. When you get this error it means that the LSN read does not agree with what is in the distribution database. Dropping the subscription and recreating it normally clears this error.  SignatureHilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 > Yesterday, we attempted to add a new table to an existing publication. > We then created the table on the subscriber and populated it manually. [quoted text clipped - 12 lines] > > Has anyone seen this error before? That part makes since. However this error does not tell me what subscription it is tripping over. I am guessing that it is associated with one of the publications that I added a table too; but I am not sure of this. Is there anyway to determine this for certain? -ms > I've encountered this. Basically the log reader writes the last LSN read > from the log into the distribution database. When you get this error it [quoted text clipped - 32 lines] > > > > Has anyone seen this error before? Its not tripping over a transaction, rather the log on the publisher. You could issue sp_repldone (look in bol for an example of how to use this), you can also carefully hack the system table to put the LSN in the distribution database with what is in the log. I normally recommend you have PSS hold your hand or advise you when you do this. SignatureHilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 > That part makes since. > [quoted text clipped - 42 lines] >> > >> > Has anyone seen this error before? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.