Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Problem restoring: LSN passed to log scan is invalid Expand / Collapse
Author
Message
Posted Thursday, November 10, 2005 7:44 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

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

Post #236278
Posted Monday, November 14, 2005 8:00 AM
SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, May 18, 2007 3:36 PM
Points: 10,039, Visits: 1
No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!
Post #236855
Posted Tuesday, November 29, 2005 11:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, November 22, 2006 3:40 AM
Points: 1, Visits: 1

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!!!

Post #240447
Posted Tuesday, November 29, 2005 12:07 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

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.

Post #240474
Posted Tuesday, November 29, 2005 2:35 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 9:02 AM
Points: 2,040, Visits: 1,668
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
Post #240518
Posted Tuesday, November 29, 2005 4:06 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, December 10, 2011 6:38 AM
Points: 215, Visits: 633

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).

Post #240551
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse