Error while running dbcc checkdb

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

Error while running dbcc checkdb

Author

Topic

vijay4457
Starting Member

3 Posts

Posted - 2011-03-10 : 06:26:06

while running dbcc checkdb on database
it gives error message as
DBCC results for 'nrega'.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'nrega'.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x8492367c; actual: 0x8495c02c). It occurred during a read of page (1:781) in database ID 21 at offset 0x0000000061a000 in file 'E:\SQL DATABASE\nrega\nrega.mdf:MSSQL_DBCC21'. 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.

Kindly tell me to resolve this problem.

vijay

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-10 : 07:01:53

Can you try setting the DB to single user mode and running DBCC CheckDB ('Database Name') WITH TABLOCK, NO_INFOMSGS, ALL_ERRORMSGS

--
Gail Shaw
SQL Server MVP

vijay4457
Starting Member

3 Posts

Posted - 2011-03-13 : 05:11:19

Sir,
Whit this command still same problem as mentioned earlier.

quote:
Originally posted by GilaMonster

Can you try setting the DB to single user mode and running DBCC CheckDB ('Database Name') WITH TABLOCK, NO_INFOMSGS, ALL_ERRORMSGS

--
Gail Shaw
SQL Server MVP

vijay

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-13 : 05:40:05

When you ran it with TABLOCK? Shouldn't be possible. The error was on the database snapshot and when run with tablock it doesn't create a snapshot.

Post the command you ran and the exact output

--
Gail Shaw
SQL Server MVP

vijay4457
Starting Member

3 Posts

Posted - 2011-03-14 : 06:29:34

running DB to single user mode
DBCC CheckDB ('nrega') WITH TABLOCK, NO_INFOMSGS, ALL_ERRORMSGS

it gives error mesaage as

Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 305957677629440, alloc unit ID 24482700918784 (type In-row data). Page (1:386) is missing a reference from previous page (1:578). Possible chain linkage problem.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 305957677629440, alloc unit ID 24482700918784 (type In-row data): Page (1:578) could not be processed. See other errors for details.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 305957677629440, alloc unit ID 305957677629440 (type In-row data). Page (1:578) was not seen in the scan although its parent (1:366) and previous (1:384) refer to it. Check any previous errors.
Msg 8944, Level 16, State 18, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 305957677629440, alloc unit ID 305957677629440 (type In-row data), page (1:578), row 3. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 50 and 98.
Msg 8944, Level 16, State 18, Line 1
Table error: Object ID 373576369, index ID 1, partition ID 305957677629440, alloc unit ID 305957677629440 (type In-row data), page (1:578), row 3. Test (columnOffsets->offTbl [varColumnNumber] >= priorOffset) failed. Values are 50 and 98.
CHECKDB found 0 allocation errors and 5 consistency errors in table 'HP10Applicants' (object ID 373576369).
Msg 8928, Level 16, State 1, Line 1
Object ID 670625432, index ID 1, partition ID 325425085022208, alloc unit ID 325425085022208 (type In-row data): Page (1:1813) could not be processed. See other errors for details.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 670625432, index ID 1, partition ID 325425085022208, alloc unit ID 325425085022208 (type In-row data). Page (1:1813) was not seen in the scan although its parent (1:269) and previous (1:1808) refer to it. Check any previous errors.
Msg 8944, Level 16, State 16, Line 1
Table error: Object ID 670625432, index ID 1, partition ID 325425085022208, alloc unit ID 325425085022208 (type In-row data), page (1:1813), row 3. Test (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 98973 and 264.
Msg 8944, Level 16, State 16, Line 1
Table error: Object ID 670625432, index ID 1, partition ID 325425085022208, alloc unit ID 325425085022208 (type In-row data), page (1:1813), row 3. Test (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 98973 and 264.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 670625432, index ID 1, partition ID 325425085022208, alloc unit ID 325425085022208 (type In-row data). Page (1:1814) is missing a reference from previous page (1:1813). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 5 consistency errors in table 'HP10MustRoll1011' (object ID 670625432).
CHECKDB found 0 allocation errors and 10 consistency errors in database 'NREGA'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (NREGA).

Kinldy provide me the sol.
thansk
Vijay

quote:
Originally posted by vijay4457

while running dbcc checkdb on database
it gives error message as
DBCC results for 'nrega'.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'nrega'.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x8492367c; actual: 0x8495c02c). It occurred during a read of page (1:781) in database ID 21 at offset 0x0000000061a000 in file 'E:\SQL DATABASE\nrega\nrega.mdf:MSSQL_DBCC21'. 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.

Kindly tell me to resolve this problem.

vijay

vijay

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-14 : 09:43:06

Ok, you have two pages damaged in that database, it's not repairable without data loss. Do you have a clean backup? That's a backup from before the corruption started.

How critical is the data in the tables HP10Applicants and HP10MustRoll1011?

--
Gail Shaw
SQL Server MVP

rahulrajpal08
Starting Member

8 Posts

Posted - 2011-03-22 : 07:10:14

Read the below article to overcome the above issue:
unspammed

Database expert

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-22 : 08:15:37

Please ignore that article, utter garbage.

The solution to logical consistency errors is NOT to buy an untested, unproven database recovery tool.
That is not a technical article, it's an advertisement for database recovery tool, nothing more.

CheckDB can repair these errors, both the ones in this thread and the ones listed in that article, albeit with data loss. Since the data on the pages is already damaged by the time those errors appear, a data recovery tool is not going to help.

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources