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
 CHECKDB fails with latch error, then succeeds
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

28 Posts

Posted - 10/08/2012 :  12:31:16  Show Profile  Reply with Quote
Last night, my nightly CHECKDB errored out:

Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Unable to read and latch page (1:1151632) with latch type SH. Latch failed.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 1 consistency errors in database 'MyDatabase'.

I manually ran CHECKDB this morning and got no errors:

CHECKDB found 0 allocation errors and 0 consistency errors in database 'MyDatabase'.

Do I have reason to be worried? Is there a way of figuring out what caused the CHECKDB failure last night? CHECKDB on the system databases found no problems, tempdb is set to unrestricted growth and there is plenty of space on the drive where tempdb lives.

Edited by - dlh on 10/08/2012 12:32:45

Starting Member

3 Posts

Posted - 10/10/2012 :  09:03:10  Show Profile  Reply with Quote
you also check other repair tools:
  • Run DBCC CHEKCTABLE state to repair SQL table
  • Or Restore from a old backup

if not. last option you restore sql database see
Go to Top of Page

Starting Member

28 Posts

Posted - 10/11/2012 :  21:13:53  Show Profile  Reply with Quote
Sorry, but I'm not sure what to do with this advice. From what I can tell, there's no table, index or page that is associated with this error.

And the error appears to have been short-term, so I don't want to roll back and lose work unless it's absolutely essential.

I do want to understand why it happened and whether it might happen again.
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.02 seconds. Powered By: Snitz Forums 2000