dbcc check failed

Question

Post reply

dbcc check failed

Sam Greene

SSCertifiable

Points: 5252
More actions
November 16, 2006 at 8:51 am

#61981

Hi,
We've applied some hotfixes to a development system and now when we run queries on 2 tables we're getting errors.
dbcc checkdb returns a whole lot of errors and recommends to use the repair with data loss option - but we'd like to recover if we can.
I tried backing up the tables and restoring them as another db - it seems fine after that, but I don't know if we've lost any data. I tried to run the compare_db script i found on this site, but of course that doesn't work . I see that the dbcc results say 0 allocation and 801 consistency errors. Can these be fixed without destroying data?
Thanks for any insight.
Sam

--from somewhat query with ~6 joins query
Server: Msg 601, Level 12, State 3, Line 1
Could not continue scan with NOLOCK due to data movement.
--from select * from xx_admissions
Server: Msg 823, Level 24, State 2, Line 1
I/O error 1450(Insufficient system resources exist to complete the requested service.) detected during read at offset 0x00000140dfe000 in file 'G:\Program Files\Microsoft SQL Server\MSSQL\Data\MAC_Ticketing_Data.MDF'.
Connection Broken
--from check dbcc
--a whole bunch of these lines
Could not read and latch page (1:663520) with latch type UP. ?? failed.
Server: Msg 8986, Level 16, State 1, Line 1
Too many errors found (201) for object ID 0. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS".
Server: Msg 2533, Level 16, State 1, Line 1
--then a bunch of these
Table error: Page (1:662992) allocated to object ID 21575115, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:662993) allocated to object ID 21575115, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
--Then these
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 21575115, index ID 1. Page (1:662992) was not seen in the scan although its parent (1:662326) and previous (1:662991) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 21575115, index ID 1. Index node page (1:662326), slot 155 refers to child page (1:662993) and previous child (1:662992), but they were not encountered.
CHECKDB found 0 allocation errors and 254 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
There are 1327 rows in 27 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 1577 rows in 96 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 6403 rows in 138 pages for object 'syscolumns'.
--etc etc
DBCC results for 'xx_admission'.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 21575115, index ID 1. Index node page (1:662806), slot 47 refers to child page (1:663013) and previous child (1:663012), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 21575115, index ID 1. Index node page (1:662806), slot 48 refers to child page (1:663014) and previous child (1:663013), but they were not encountered.
Too many errors found (201) for object ID 21575115. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS".
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:407448) allocated to object ID 430624577, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 430624577, index ID 1. Page (1:407448) was not seen in the scan although its parent (1:406816) and previous (1:407351) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 430624577, index ID 1. Page (1:407449) is missing a reference from previous page (1:407448). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 430624577, index ID 1. Page (1:407450) was not seen in the scan although its parent (1:406816) and previous (1:407449) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 430624577, index ID 1. Index node page (1:406816), slot 155 refers to child page (1:407451) and previous child (1:407450), but they were not encountered.
There are 7 rows in 1 pages for object 'ts_series_allotment'.
DBCC results for 'xx_order_admission'.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 430624577, index ID 1. Index node page (1:408067), slot 136 refers to child page (1:408595) and previous child (1:408594), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 430624577, index ID 1. Index node page (1:408067), slot 137 refers to child page (1:408596) and previous child (1:408595), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 430624577, index ID 1. Index node page (1:408067), slot 138 refers to child page (1:408597) and previous child (1:408596), but they were not encountered.
Too many errors found (201) for object ID 430624577. To see all error messages rerun the statement using "WITH ALL_ERRORMSGS".
There are 250098 rows in 15730 pages for object 'xx_order_admission'.
CHECKDB found 0 allocation errors and 221 consistency errors in table 'xx_order_admission' (object ID 430624577).
--snip
CHECKDB found 0 allocation errors and 801 consistency errors in database 'MYDB'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (MYDB).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

--from compare_db script
30. TABLE: [ts_admission]
1341200 rows in Mac_Ticketing
1341200 rows in MAC_CLEAN
Server: Msg 601, Level 12, State 3, Line 1
Could not continue scan with NOLOCK due to data movement.
Server: Msg 601, Level 12, State 1, Line 1
Could not continue scan with NOLOCK due to data movement.
Server: Msg 823, Level 24, State 2, Line 1
I/O error 1450(Insufficient system resources exist to complete the requested service.) detected during read at offset 0x00000140ff4000 in file 'G:\Program Files\Microsoft SQL Server\MSSQL\Data\MAC_Ticketing_Data.MDF'.
Connection Broken

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

SQL ORACLE One Orange Chip Points: 27807 More actions · Answer 1

Is the following link helpful?

http://support.microsoft.com/kb/276992

Sam Greene SSCertifiable Points: 5252 More actions · Answer 2

I am running:

And that says it only applies to 7, as do many of the knowledge base articles I've come across.

But thanks!

Sam Greene SSCertifiable Points: 5252 More actions · Answer 3

We have turned this problem over to a vendor to fix, as they broke it in the first place .

thanks.

Balmukund SSCertifiable Points: 6648 More actions · Answer 4

I am not sure if it is caused by hardware failure. Most possible YES.

How much RAM do you have? If you have more than 4 Gb of RAM and you are using AWE I will highly recommend you to apply SP1 for Windows 2003 OS.

MS has known issue of corruption on

895575 A process that runs in the Physical Address Extension (PAE) kernel may experience memory corruption in Windows Server 2003

http://support.microsoft.com/?id=895575

Data is corrupted when PAE is enabled on a Windows Server 2003-based computer

http://support.microsoft.com/?id=834628