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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-09-22 : 10:19:01
|
| Ben writes "Dbcc checkdb showed a database to have consistency errors, however running repair_allow_data_loss resulted in the following errorServer: Msg 8966, Level 16, State 1, Line 2Could not read and latch page (1:1370) with latch type SH. sysindexes failed.DBCC execution completed. If DBCC printed error messages, contact your system administrator.Please could you tell me how to fix it, and how it occurred in the first place?Thanks" |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2006-09-23 : 16:47:38
|
| Do you have a backup of this database? Is it a production database?Run the DBCC CHECKDB again and post any errors. Don't run with "repair_allow_data_loss" option this time. It looks somewhat familiar to this:http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=53271MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2006-09-23 : 20:17:37
|
| Repair won't fix it - you need to restore from your backups. Its a damaged page in one of the critical system tables (sysindexes). These errors are almost 100% caused by h/w going bad. Run full disk diagnostics, look for errors in the SQL Server errorlog and Windows event logs.If you don't have any backups, script out a new database and extract as much as you can from the damage one (and get a backup strategy)Thanks |
|
|
|
|
|
|
Could not read and latch page (1:1370) with latch type SH