Post reply

Problem restoring: LSN passed to log scan is invalid

  • November 10, 2005 at 7:44 am

    #110748

    I am getting the following error when trying to re-attach a database(DB has data file, Index file, and 2 separate log files).  Server is SQL2000 SP3a, OS is Windows 2003

    The LSN (88:289:1) passed to log scan in database '<DBname>' is invalid.

    I get the error when attaching, and I get the same error when trying to restore from backup. 

    I have tried restoring to different server but get same error.  I have also tried attaching just the data file but get same error.  I have also tried using single file restore command and get the same error.  I have tried re-setting status and get an error message and the database goes back to suspect/loading mode.

    I am out of ideas and thinking Microsoft Suppt is best option unless someone has better ideas

    Any help is greatly appreciated

  • November 14, 2005 at 8:00 am

    This was removed by the editor as SPAM

  • November 29, 2005 at 11:13 am

    #606492

    You have to read the following link:

    http://dbforums.com/t519971.html

    We had the same problem and we followed this solution 1 of Roberto Carrasco and it run!!!

  • November 29, 2005 at 12:07 pm

    #606516

    Couldn't get the solutions on line to work.  The problem ended up being the corrupt log file, but I had to get rid of the secondary index file as well.  Ended up just attaching the mdf and using the undocumented command to rebuild the log file

    Thanks to everyone and Microsoft for the help getting this one solved.

  • November 29, 2005 at 2:35 pm

    #606550

    I'm curious - did the PSS person warn you about the consequences of rebuilding the log? Were you instructed to do anything else after rebuilding the log?

    Thanks

    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

  • November 29, 2005 at 4:06 pm

    #606575

    Yes I was warned about the consequences of rebuilding the log, and for this instance that was acceptable.

    After getting the database to come up available, I ended up creating a new database, log file, filegroup, and new file for the indexes.  I pushed the tables to the new database and rebuilt the indexes(Microsoft Tech Agreed this would help with more stable database and possibly avoid future corruption).

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply