Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Could not read and latch page (1:1370) with latch type SH
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Ask SQLTeam Question

0 Posts

Posted - 09/22/2006 :  10:19:01  Show Profile  Visit AskSQLTeam's Homepage  Reply with Quote
Ben writes "Dbcc checkdb showed a database to have consistency errors, however running repair_allow_data_loss resulted in the following error

Server: Msg 8966, Level 16, State 1, Line 2
Could 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?


Pointy Haired Yak DBA

4184 Posts

Posted - 09/23/2006 :  16:47:38  Show Profile  Visit derrickleggett's Homepage  Send derrickleggett an AOL message  Send derrickleggett a Yahoo! Message  Reply with Quote
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:


When life gives you a lemon, fire the DBA.
Go to Top of Page

Yak with Vast SQL Skills

899 Posts

Posted - 09/23/2006 :  20:17:37  Show Profile  Visit paulrandal's Homepage  Reply with Quote
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)

Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000