September 14, 2013 at 7:30 pm
We had found logical consistency errors in the database when we ran dbcc checkdb.
The application vendor told us to rebuild an index for a particular table but we ended up with the following error.Any further way out:
Executing the query "ALTER INDEX [PK__ERRORLOG] ON [dbo].[GSX_ERRORL..." failed with the following error: "SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0x10001555). It occurred during a read of page (1:9381968) in database ID 7 at offset 0x000011e50a0000 in file 'P:\\MSSQL10_50.MSSQLSERVER\\MSSQL\\DATA\\GSX_Prod_Data.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.
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.
September 15, 2013 at 5:40 am
Please run the following and post the full and complete, unedited output
DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
You can also point out to the vendor who recommended that, that rebuilding indexes will not remove corruption and hence they should please refrain from offering incorrect recommendations in future.
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 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply