Corrupt table in database

%3CLINGO-SUB%20id%3D%22lingo-sub-3363706%22%20slang%3D%22en-US%22%3ECorrupt%20table%20in%20database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3363706%22%20slang%3D%22en-US%22%3E%3CP%3Eget%20this%20error%20after%20select%20script%3C%2FP%3E%3CP%3E%22SQL%20Server%20detected%20a%20logical%20consistency-based%20I%2FO%20error%3A%20torn%20page%20(expected%20signature%3A%200xaaaaaaaa%3B%20actual%20signature%3A%200x1004cd6e).%20It%20occurred%20during%20a%20read%20of%20page%20(1%3A1520237)%20in%20database%20ID%20137%20at%20offset%200x000002e64da000%20in%20file%20'C%3A%5CProgram%20Files%5CMicrosoft%20SQL%20Server%5CMSSQL12.MSSQLSERVER2014%5CMSSQL%5CDATA%5CCOMDAT.mdf'.%20Additional%20messages%20in%20the%20SQL%20Server%20error%20log%20or%20system%20event%20log%20may%20provide%20more%20detail.%20This%20is%20a%20severe%20error%20condition%20that%20threatens%20database%20integrity%20and%20must%20be%20corrected%20immediately.%20Complete%20a%20full%20database%20consistency%20check%20(DBCC%20CHECKDB).%20This%20error%20can%20be%20caused%20by%20many%20factors%3B%20for%20more%20information%2C%20see%20SQL%20Server%20Books%20Online.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewhat%20could%20cause%20this%20and%20how%20can%20i%20fix%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3373482%22%20slang%3D%22en-US%22%3ERe%3A%20Corrupt%20table%20in%20database%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3373482%22%20slang%3D%22en-US%22%3EHi%20Tiyanjana%2C%3CBR%20%2F%3EThe%20causes%20of%20this%20issue%20could%20be%3CBR%20%2F%3E1-%20file%20system%20corruption%3CBR%20%2F%3E2-%20hardware%20system%20issues%20including%20storage%2C%20SAN%2C%20disk%2C%20raid%20controller%2C%20etc.%3CBR%20%2F%3E3-%20driver%20issues%3CBR%20%2F%3E4-%20corrupted%20memory%20pages%3CBR%20%2F%3E5-%20problems%20with%20the%20SQL%20Server%20Engine.%3CBR%20%2F%3EFor%20fixing%20it%2C%20you%20can%20use%20the%20steps%20in%20this%20Microsoft%20article%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Ftroubleshoot%2Fsql%2Fadmin%2Ftroubleshoot-dbcc-checkdb-errors%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Ftroubleshoot%2Fsql%2Fadmin%2Ftroubleshoot-dbcc-checkdb-errors%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

get this error after select script

"SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x1004cd6e). It occurred during a read of page (1:1520237) in database ID 137 at offset 0x000002e64da000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER2014\MSSQL\DATA\COMDAT.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."

 

what could cause this and how can i fix it?

1 Reply
Hi Tiyanjana,
The causes of this issue could be
1- file system corruption
2- hardware system issues including storage, SAN, disk, raid controller, etc.
3- driver issues
4- corrupted memory pages
5- problems with the SQL Server Engine.
For fixing it, you can use the steps in this Microsoft article:
https://docs.microsoft.com/en-US/troubleshoot/sql/admin/troubleshoot-dbcc-checkdb-errors