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

Errors

Author

Topic

willieww
Starting Member

1 Post

Posted - 2011-02-22 : 04:19:08

Hello,

I am getting the following errors, is there a way to fix it without losing data?

NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.4035
Report was generated on "SERVER\EVOLUTION".
Maintenance Plan: WW
Duration: 00:08:03
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity Task (SERVER\EVOLUTION)
Check Database integrity on Local server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All databases
Include indexes
Task start: 2011-02-21T20:30:12.
Task end: 2011-02-21T20:37:19.
Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594529644544 (type Unknown), page (1:414925). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270473 and -4.
Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data): Page (1:414893) could not be processed. See other errors for details.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data), page (1:414893). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270473 and -4.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Page (1:414893) was not seen in the scan although its parent (1:390872) and previous (1:414892) refer to it. Check any previous errors.
Table error: page (1:414894) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 50 refers to child page (1:414894) and previous child (1:414893), but they were not encountered.
Table error: page (1:414895) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 51 refers to child page (1:414895) and previous child (1:414894), but they were not encountered.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Page (1:414896) is missing a reference from previous page (1:414895). Possible chain linkage problem.
Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data): Page (1:414917) could not be processed. See other errors for details.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data), page (1:414917). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 46270473 and -4.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Page (1:414917) was not seen in the scan although its parent (1:390872) and previous (1:414916) refer to it. Check any previous errors.
Table error: page (1:414918) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 74 refers to child page (1:414918) and previous child (1:414917), but they were not encountered.
Table error: page (1:414919) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 75 refers to child page (1:414919) and previous child (1:414918), but they were not encountered.
Table error: page (1:414920) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 76 refers to child page (1:414920) and previous child (1:414919), but they were not encountered.
Table error: page (1:414921) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 77 refers to child page (1:414921) and previous child (1:414920), but they were not encountered.
Table error: page (1:414922) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 78 refers to child page (1:414922) and previous child (1:414921), but they were not encountered.
Table error: page (1:414923) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 79 refers to child page (1:414923) and previous child (1:414922), but they were not encountered.
Table error: page (1:414924) allocated to object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 80 refers to child page (1:414924) and previous child (1:414923), but they were not encountered.
Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data): Page (1:414925) could not be processed. See other errors for details.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Index node page (1:390872), slot 81 refers to child page (1:414925) and previous child (1:414924), but they were not encountered.
Table error: Object ID 802101898, index ID 1, partition ID 72057594638565376, alloc unit ID 72057594643742720 (type In-row data). Page (1:414926) is missing a reference from previous page (1:414925). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 28 consistency errors in table '_btblInvoiceLines' (object ID 802101898).
CHECKDB found 0 allocation errors and 29 consistency errors in database 'WTell SQL'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WTell SQL).". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2011-02-22 : 11:21:25

Repost in Data Corruption. You're likely to get immediate responses.

Terry

-- You can't be late until you show up.

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2011-02-22 : 15:56:52

Your best option is to restore from your backups and apply transaction logs up to current. Perform a tail-log backup before starting the restore and you should be able to restore with no data loss.

That is assuming you have a clean backup without the integrity errors to start from.

Jeff

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-02-22 : 17:47:33

I've moved the topic to the "Data Corruption Issues" forum.

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

Subscribe to my blog

rahulrajpal08
Starting Member

8 Posts

Posted - 2011-02-23 : 13:57:55

Database corruption can be dangerous. DBCC error messages primarily depict the exact cause of corruption and the parts of database that have been affected by corruption. The only easy way to overcome database corruption is restoration from a complete online backup. However, if there is no backup, then there is a real problem. I read very good article on resolution for corruption, if you wish to read:
unspammed

Database expert

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-22 : 08:26:19

Rather don't read that, it's far from a good article.

That article is incomplete and misleading, deleting a table is in no way the best solution for a corrupt page and it makes no mention of CheckDB's repair options. In fact it reads like just an advertisement for a data recovery tool.

The article refers to a different version of SQL than this question does. The question refers to a SQL 2005 database, that article is on a SQL 2000-specific corruption (there's no sysindexes table in SQL 2005)

The errors that the article badly handles are not the ones referred to in the initial post here. They are totally different problems with different resolutions.

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources