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

logical consistency-based I/O error: incorrect checksum Expand / Collapse
Author
Message
Posted Friday, September 14, 2012 5:04 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 25, 2014 3:12 AM
Points: 3, Visits: 171
Hi,

Recently got the following alert

DESCRIPTION: SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x03c8720b; actual: 0x887d3f27). It occurred during a read of page (1:73824) in database ID 2 at offset 0x000000240c0000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\tempdb.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.


Ran DBCC CHECKDB on all databases, no problems reported.

According to my colleagues no hardware issues are apparent on the server.

I'm unsure as to what I need to do next (very much a part time, 'accidental' dba)

Any advice appreciated.

Thanks



Post #1359172
Posted Friday, September 14, 2012 5:13 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:45 AM
Points: 40,173, Visits: 36,567
Did you run checkDB on TempDB?


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1359178
Posted Friday, September 14, 2012 5:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 25, 2014 3:12 AM
Points: 3, Visits: 171
I did. No errors.


Post #1359180
Posted Friday, September 14, 2012 6:12 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:45 AM
Points: 40,173, Visits: 36,567
Probably because the temp table that had the error was dropped before you could run checkDB.

Still, indicates that there's something not right about the IO subsystem. Check logs, check drivers, etc.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1359207
Posted Friday, September 14, 2012 6:39 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 25, 2014 3:12 AM
Points: 3, Visits: 171
Thanks for your help.

I'll see what I can find.



Post #1359222
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse