Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
william.weber
Starting Member
3 Posts |
 Posted - 2008-01-22 : 16:50:22
|
| This morning one of our client's database appeared as Suspect. I checked the event log and saw the following error:Could not redo log record (413:835:2), for transaction ID (0:156861), on page (1:1246), database 'CLP' (database ID 26). Page: LSN = (412:2642:4), type = 1. Log: OpCode = 4, context 2, PrevPageLSN: (412:12236:2). Restore from a backup of the database, or repair the database.I then tried to run a DBCC CHECKDB on the database and got the following output:Msg 7987, Level 16, State 1, Line 1System table pre-checks: Object ID 13 has chain linkage mismatch. (1:339)->next = (1:771), but (1:771)->prev = (1:341). Check statement terminated due to unrepairable error.DBCC results for 'CLP'.CHECKDB found 0 allocation errors and 0 consistency errors in database 'CLP'.After a bit of research I began to get very sad, for a number of reasons. First I can't find much information on this error and what there is implies that I'm totally up the creek. Secondly and worst of all, backups have not been working so we don't have a viable backup of the database.I did go as far as to run repair_allow_data_loss and received the same Msg: 7897 error as above.Is there any hope? Can this be repaired? Any help is greatly appreciated.-Will |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2008-01-22 : 19:08:31
|
| what version sql server? |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-22 : 23:18:06
|
| Did you see disk related error in windows event logs? |
|
|
|
william.weber
Starting Member
3 Posts |
Posted - 2008-01-23 : 09:52:43
|
| Sorry for the omission. We are using SQL 2005 on a Windows 2003 server run on a virtual server (microsoft virtual server).There were no disk errors in the event log, the only errors of any kind in the event log were multiple iterations of the first message in my original post about "could not redo log record."Thanks for the replies. |
|
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2008-03-07 : 01:52:28
|
| Have you tried to restart the SQL Server?Jack Vamvas--------------------Search IT jobs from multiple sources- http://www.ITjobfeed.com |
|
|
|
william.weber
Starting Member
3 Posts |
Posted - 2008-03-07 : 09:39:07
|
| Just to close this one out in case someone finds it in a search. The database was unrecoverable. We brought in Microsoft Support and they tried a number of things to get our data back but in the end they had to give up. The database was restored from the last good backup (months back) and then data was re-entered by hand from hardcopy. |
|
|
|
|
|
|
|
|
Suspect database has turned into a nightmare