samedi 31 janvier 2015

SQL Server: Invalid Log Scan Number (...) passed to log scan in database (...) is not valid


We are getting a large number of the below errors on one of our primary production databases. CheckDB is completely clean.


We thought it was related to replication so we shut it down using sp_removedbreplication and the problem went away. For other reasons, we did a restore from last night backup which resurrected replication again. Immediately the errors returned and have persisted despite my removing replication again.



  • Error: 9003, Severity: 20, State: 1.

  • The log scan number (390576:5234:44) passed to log scan in database 'XXXX' 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.


I'm not finding much on the web related to this except articles related to the master database and SQL being unable to start and replication issues.


Any advice would be tremendously appreciated!





Aucun commentaire:

Enregistrer un commentaire