October 26, 2012 at 3:38 pm
Hi All,
While doing a rebuild index on a DB, I keep getting the error message below. How can I fix this issue?
Error: 0xC002F210 at Rebuild Index Task, Execute SQL Task: Executing the query "ALTER INDEX [X1_TIMEITEM] ON [dbo].[TIMEITEM..." failed with the following error: "SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x09b00d7a; actual: 0x2774d8f0). It occurred during a read of page (6:143127) in database ID 7 at offset 0x00000045e2e000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\DB_2.ndf'. 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.
The statement has been terminated.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Task failed: Rebuild Index Task
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
Thanks in Advanced
October 26, 2012 at 4:18 pm
As the error message states, it appears that you have a database consistency issue with the database. Are you running DBCC CHECKDB on a regular basis? If the index is not being used to enforce a primary key constraint, you can try to drop the index and re-create it instead of rebuilding it. You should also have someone review the hardware that the data file resides on. These types of error messages typically indicate a hardware problem. I have also seen similar errors when there was an issue with a memory module and the copy of the data page in the buffer was corrupted.
How frequently have you been receiving the errors?
I would definitely run DBCC CHECKDB against the database as soon as you can find an open window to do so.
October 26, 2012 at 4:37 pm
Here's a link to a previous post that you'll want to take a look at:
http://www.sqlservercentral.com/Forums/Topic1232926-2893-1.aspx#bm1233046
Gail Shaw's advice is spot on: "For recovery without data loss, take a tail-log backups and restore from backup, either full database, filegroup, file or page and then roll all the logs forward".
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply