July 16, 2015 at 3:30 pm
I've been hitting a problem where a CREATE INDEX is failing. The debug error exception shows the error is invalid because expected and actual are a match, not a miss-match. This is killing me. I've flattened and re-created the entire database (file groups, files, tables) and can't get past this. Any tips on how to handle this?
The server is Windows 2012 R2, Sql Server 2014 Enterprise w/sp1. Vertex 3 SSD's.
.NET Exception Message:
The operating system returned error incorrect checksum (expected: 0x2ca0d355; actual: 0x2ca0d355) to SQL Server during a read at offset 0x0000007605c000 in file 'h:\SqlSvr\Data\ClusterIdx.ndf'. 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.
Could not create constraint or index. See previous errors.
The statement has been terminated.
Output from CHECKDB
"CHECKDB found 0 allocation errors and 0 consistency errors in database 'EVRoute'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator."
August 6, 2015 at 10:04 pm
If you have run the same DDL on the same hardware and received the same result, do you receive the same message when you run the same DDL upon completely different hardware or a completely different OS?
If reproducible on completely different hardware, you should provide Microsoft SQL Server Support with the DDL script.
If not reproducible on a different OS running on completely different hardware, but is reproducible when just that different hardware has its OS upgraded to your current OS, you should open a support case with Microsoft Platforms Support.
I am certain many readers would be willing to run the same DDL on their hardware, OS version, and/or SQL Server version. Can you provide readers with a DDL script that causes this problem?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply