Corruption:missing a reference from previous page

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

Corruption:missing a reference from previous page

Author

Topic

sbalaji
Starting Member

48 Posts

Posted - 2009-04-21 : 16:40:32

Hi,

Check the below errors

Is there any way to correct this,I have tried few solution from the blogs and threads,but i am not able to make it work.

DBCC CHECKDB (Corrupted_DB) WITH NO_INFOMSGS, ALL_ERRORMSGS

Results
----------------------------------------------------------------------
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 41, index ID 2, partition ID 562949956108288, alloc unit ID 72057594042515456 (type In-row data). Page (1:3235) is missing a reference from previous page (1:3332). Possible chain linkage problem.
Msg 8928, Level 16, State 1, Line 1
Object ID 41, index ID 2, partition ID 562949956108288, alloc unit ID 72057594042515456 (type In-row data): Page (1:3332) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 41, index ID 2, partition ID 562949956108288, alloc unit ID 72057594042515456 (type In-row data), page (1:3332). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 41, index ID 2, partition ID 562949956108288, alloc unit ID 72057594042515456 (type In-row data). Page (1:3332) was not seen in the scan although its parent (1:160) and previous (1:3335) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'sys.syscolpars' (object ID 41).

Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 75, index ID 1, partition ID 281474981625856, alloc unit ID 281474981625856 (type In-row data). Page (1:3388) is missing a reference from previous page (1:3389). Possible chain linkage problem.
Msg 8928, Level 16, State 1, Line 1
Object ID 75, index ID 1, partition ID 281474981625856, alloc unit ID 281474981625856 (type In-row data): Page (1:3389) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 75, index ID 1, partition ID 281474981625856, alloc unit ID 281474981625856 (type In-row data), page (1:3389). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 75, index ID 1, partition ID 281474981625856, alloc unit ID 281474981625856 (type In-row data). Page (1:3389) was not seen in the scan although its parent (1:1684) and previous (1:3387) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'sys.sysmultiobjrefs' (object ID 75).

Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1932898303, index ID 4, partition ID 72057594374258688, alloc unit ID 72057594457489408 (type In-row data). Page (1:2159) is missing a reference from previous page (1:2280). Possible chain linkage problem.
Msg 8928, Level 16, State 1, Line 1
Object ID 1932898303, index ID 4, partition ID 72057594374258688, alloc unit ID 72057594457489408 (type In-row data): Page (1:2280) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1932898303, index ID 4, partition ID 72057594374258688, alloc unit ID 72057594457489408 (type In-row data), page (1:2280). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29362185 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1932898303, index ID 4, partition ID 72057594374258688, alloc unit ID 72057594457489408 (type In-row data). Page (1:2280) was not seen in the scan although its parent (1:3766) and previous (1:2157) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'RGML' (object ID 1932898303).

CHECKDB found 0 allocation errors and 12 consistency errors in database 'Corrupted_DB'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Corrupted_DB).
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4a3c01d2; actual: 0x2e3c0119). It occurred during a read of page (1:3389) in database ID 13 at offset 0x00000001a7a000 in file 'E:\SQL\data\Corruption.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.

regards
balaji.S

sbalaji
Starting Member

48 Posts

Posted - 2009-04-21 : 16:58:41

Hi,

DBCC CHECKDB (Corrupted_DB,REPAIR_ALLOW_DATA_LOSS )

corrected the issue,now there is no inconsistency,Is there any way from the above we can know what's the cause of corruption?.

thanks,

regards
balaji.s

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2009-04-27 : 06:26:40

It was your I/O subsystem - 100% certain - that's why you got a page checksum failure. You'll need to figure out why it happened (bad drivers, failing drive, etc) and correct it so it doesn't happen again in a way you can't fix.

Btw - you need to start taking backups.

Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)
SQL Server MVP, Microsoft Regional Director, Contributing Editor of TechNet Magazine
Author of SQL 2005 DBCC CHECKDB/repair code
Author & Instructor of Microsoft Certified Master - Database course

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources