dbcc check errors - SQL Server Forums

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

dbcc check errors

Author

Topic

albertkohl
Aged Yak Warrior

740 Posts

Posted - 2010-10-23 : 15:15:29

i ran a dbcc check on a database and got the below errors... now what?!

DBCC results for 'NMOL_SESSION'.
Msg 8928, Level 16, State 1, Line 1
Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data): Page (1:7128) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data), page (1:7128). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data). Page (1:7128) was not seen in the scan although its parent (1:18739) and previous (1:19255) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data). Page (1:19256) is missing a reference from previous page (1:7128). Possible chain linkage problem.
There are 422642 rows in 8374 pages for object "NMOL_SESSION".
CHECKDB found 0 allocation errors and 4 consistency errors in table 'NMOL_SESSION' (object ID 197575742).

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-10-23 : 15:26:21

I edited your post to remove the code tags (made the post much too wide) and changed the forum to Data Corruption Issues. Code tags are only needed to retain formatting, which isn't needed for your output.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

albertkohl
Aged Yak Warrior

740 Posts

Posted - 2010-10-23 : 15:27:42

thanks tara, sorry for the nubbish mistake.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-10-23 : 17:10:12

Please run the following and post the full and complete output. There's at least one line missing from your post.


DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Do you have a clean backup? That's a backup that doesn't have the corruption in it.

--
Gail Shaw
SQL Server MVP

albertkohl
Aged Yak Warrior

740 Posts

Posted - 2010-10-25 : 03:24:32

honestly, i'm not sure, i dont run the dbcc check often enough to know... the table that's showing the errors is kinda expendable so if i loss data it's not a huge deal.

are there any recommendations you guys whould have to run checks like this so often, in the event of an error, notifiy me?

thanks!

Msg 8928, Level 16, State 1, Line 1
Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data): Page (1:7128) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data), page (1:7128). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data). Page (1:7128) was not seen in the scan although its parent (1:18739) and previous (1:19255) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 197575742, index ID 2, partition ID 72057594039304192, alloc unit ID 72057594040942592 (type In-row data). Page (1:19256) is missing a reference from previous page (1:7128). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'NMOL_SESSION' (object ID 197575742).
CHECKDB found 0 allocation errors and 4 consistency errors in database 'Website'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Website).

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-10-25 : 05:01:15

Despite the recommendations, I do not suggest repair with allow data loss. It should not be necessary in this case, unless there's something I've missed.

Run the following to identify the index in question, drop that index and then recreate it (not rebuild or create with drop_existing)

select object_name(object_id) as TableName, name as IndexName 
from sys.indexes 
where object_id = 197575742 and index_id = 2

Once you've done that, please run that checkDB command again and see what it returns.

As for regular checkDBs, absolutely essential. How often depends on your backup retention strategy. You should do checkDB often enough that restoring from backup is always an option. Set up a job or a maint plan an d have it alert you on failure.

--
Gail Shaw
SQL Server MVP

albertkohl
Aged Yak Warrior

740 Posts

Posted - 2010-10-25 : 15:42:45

worked perfectly, thanks!

i guess i'll start running dbcc checks prior to my full backups, seems like a good place to start... appreciate the help!

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-10-25 : 16:46:51

Glad to hear it.

Before backups is what I like to recommend. Isn't always possible, but is good place to start.

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources