locked
ERROR: The log scan number passed to log scan in database is not valid, on LOG SHIPPING Sql Server 2008 RRS feed

  • Question

  • Hi,

    Actualy there is a Log Shipping stage, and today the restore job (secondary server) failed by the next error :

    The log scan number (2096083:401:1) passed to log scan in database 'BDName' 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.
    RESTORE LOG is terminating abnormally.

    I need your help about how to fix it!!

    Wednesday, September 7, 2011 10:13 PM

Answers

  • From the error message it appears that the database is corrupt. Easiest approach would be to re-initialize the log shipping by restoring a fresh full database backup.


    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @PradeepAdiga

    • Proposed as answer by Peja Tao Friday, September 9, 2011 8:21 AM
    • Marked as answer by Peja Tao Thursday, September 15, 2011 2:26 AM
    Thursday, September 8, 2011 5:07 AM
  • I agree with Pradeep that your log file seems to be corrupted. Run DBCC CHECKDB on the principal and re-create Log shipping
    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/
    • Proposed as answer by Peja Tao Friday, September 9, 2011 8:21 AM
    • Marked as answer by Peja Tao Thursday, September 15, 2011 2:26 AM
    Thursday, September 8, 2011 6:50 AM

All replies

  • From the error message it appears that the database is corrupt. Easiest approach would be to re-initialize the log shipping by restoring a fresh full database backup.


    Pradeep Adiga
    Blog: sqldbadiaries.com
    Twitter: @PradeepAdiga

    • Proposed as answer by Peja Tao Friday, September 9, 2011 8:21 AM
    • Marked as answer by Peja Tao Thursday, September 15, 2011 2:26 AM
    Thursday, September 8, 2011 5:07 AM
  • I agree with Pradeep that your log file seems to be corrupted. Run DBCC CHECKDB on the principal and re-create Log shipping
    Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/
    • Proposed as answer by Peja Tao Friday, September 9, 2011 8:21 AM
    • Marked as answer by Peja Tao Thursday, September 15, 2011 2:26 AM
    Thursday, September 8, 2011 6:50 AM