November 16, 2010 at 4:10 am
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 ?
November 16, 2010 at 5:24 am
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
November 17, 2010 at 3:14 am
thanks.
Any more advice ?
Cheers
November 17, 2010 at 3:41 am
You can also use the TABLOCK hint so that DBCC CHECKDB does not create internal snapshots. More details here[/url]
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 17, 2010 at 4:29 am
Are you using diskeeper?
I suspect you're running into this issue. Please check what disk utilities you have installed.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply