November 8, 2007 at 1:50 pm
We are seeing the below errors in our logs. I assume the last message must be because of the first 2 messages.
Would appreciate if some can share their experience in resolving these errors?
Thanks,
Bob
======================================================
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData] REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE = OFF )
" failed with the following error: "SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:2676; actual 14616:395852048). It occurred during a read of page (1:2676) in database ID 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.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.
=====================================================
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData] REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:2653; actual 47686:707280961). It occurred during a read of page (1:2653) in database ID 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.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.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
=====================================================
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
======================================================
November 9, 2007 at 12:03 am
USE SP_IntranetMySites_WebApp ---assuming databasename
DBCC CHECKDB
Look for output to determine table name or index name.
if objectid is returned...
select object_name('objectidreturnedinerror')
dbcc checktable ('tablename')
see books online for dbcc commands... repair_fast, repair_rebuild, repair_allow_data_loss.
Sometimes just following the error will lead you there. We've had to drop and recreate indexes or primary keys ( ick, because then you have to drop foriegn keys, noclustered indexes)
Check to see if any disk media has a failure.
One trick we've used is to select from the table in ranges until we get an error. If table has 100,000 records, and error refers to an index on a specific column.... select from 1 to 50,000... if no error 50,000 to 100,000. If error 50,000 to 75,000 and break it down to find the exact record and delete and restore from a backup.
Todd Carrier
MCITP - Database Administrator (SQL 2008)
MCSE: Data Platform (SQL 2012)
November 9, 2007 at 5:57 am
Thanks for the clues. I will work on them.
-mkb
December 2, 2007 at 4:11 pm
DO NOT USE REPair_allow_data_loss.
You can try to repair the table but moving the data out and reading around the structures, but it might not work. This is really worth the $250 to call Microsoft Support to work on this if it's a production system.
December 11, 2007 at 9:49 am
Thanks for all the suggestions. I worked with MS Support to resolve the issue by repairing the table with out any data loss.
Thanks,
MB
December 11, 2007 at 10:56 am
Mind sharing with us what you did? Not that I'd necessarily recommend anyone else follow your instructions from PSS, but I'm curious what might have been wrong and how they examined the issue.
Thanks for the update and glad it worked out for you. Sorry we couldn't help more.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply