8

Running DBCC CHECKDB (dbname) WITH NO_INFOMSGS, ALL_ERRORMSGS results in this error:

Table error: Multiple IAM pages for object ID 813245952, index ID 1, partition ID 72057594073972736, alloc unit ID 72057594083213312 (type In-row data) contain allocations for the same interval. IAM pages (1:4611577) and (1:2040821). CHECKDB found 1 allocation errors and 0 consistency errors in table 'tablename' (object ID 813245952). CHECKDB found 1 allocation errors and 0 consistency errors in database 'dbname'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (dbname).

Has anyone experienced this issue before and have a solution for repair?

Note:- I have not run the statement with repair_allow_data_loss yet.

mustaccio
28.7k24 gold badges60 silver badges77 bronze badges
asked May 12, 2015 at 20:08
1
  • Dbcc tells you that data loss is your only option. Best is to restore the db from backup. This is commonly caused by hardware failure. Can you check windows event log for any trails? Refer : technet.microsoft.com/en-us/library/aa275771(v=sql.80).aspx Commented May 12, 2015 at 20:31

1 Answer 1

1

We ran into this error on SQL Server 2014, and resolved it by rebuilding the clustered index on the table.

ALTER INDEX pk_table ON dbo.table REBUILD WITH (ONLINE = OFF);

Afterwards DBCC CHECKDB (MyDatabase) ran with no errors.

Hannah Vernon
71.1k22 gold badges178 silver badges324 bronze badges
answered Jan 25, 2021 at 15:13

Your Answer

Draft saved
Draft discarded

Sign up or log in

Sign up using Google
Sign up using Email and Password

Post as a guest

Required, but never shown

Post as a guest

Required, but never shown

By clicking "Post Your Answer", you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.