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

DBCC CHECKDB resulted in error Expand / Collapse
Author
Message
Posted Tuesday, November 16, 2010 4:10 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 3:58 AM
Points: 232, Visits: 781
Database 'xyz70' is on cluster... and DBCC CHECKDB resulted in error


CHECKDB found 0 allocation errors and 0 consistency errors in database 'wslog70'.
Msg 823, Level 24, State 2, Line 1
The operating system returned error 38(error not found) to SQL Server during a read at offset 0x00000267ed6000 in file 'G:\Data\xyz70.mdf:MSSQL_DBCC33'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level 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.

Any help ?
Post #1021354
Posted Tuesday, November 16, 2010 5:24 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, January 30, 2014 8:52 AM
Points: 1,618, Visits: 20,966
Looks like there is some issue with the Hidden Snapshot that SQL Server creates while running DBCC CHECKDB. Read Paul's article here

To ensure that the database is clean, create a snapshot of the database and run DBCC CHECKDB against it.


Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
Post #1021398
Posted Wednesday, November 17, 2010 3:14 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 3:58 AM
Points: 232, Visits: 781
thanks.

Any more advice ?

Cheers
Post #1022002
Posted Wednesday, November 17, 2010 3:41 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, January 30, 2014 8:52 AM
Points: 1,618, Visits: 20,966
You can also use the TABLOCK hint so that DBCC CHECKDB does not create internal snapshots. More details here


Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
Post #1022026
Posted Wednesday, November 17, 2010 4:29 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:36 AM
Points: 41,521, Visits: 34,438
Are you using diskeeper?

I suspect you're running into this issue. Please check what disk utilities you have installed.

http://blogs.msdn.com/b/psssql/archive/2010/01/08/dbcc-check-commands-encounter-problems-and-reports-errors.aspx
http://sqlblog.com/blogs/jonathan_kehayias/archive/2009/12/10/a-tale-of-checkdb-failures-cause-by-3rd-party-file-system-drivers.aspx



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 #1022056
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse