troubleshooting Question

SQL DBCC CHECKDB finds errors that it cannot fix

Avatar of clarkincit
clarkincit asked on
Microsoft SQL Server 2008
6 Comments1 Solution2521 ViewsLast Modified:
Hello,

I am getting errors that are not able to be cleaned out with a DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS.  I am running the following statement:

DBCC CHECKDB ('dbname', REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS,NO_INFOMSGS
GO

And I am getting the output below.  I get the errors again when I run it a second time - so it's not cleaning them up.  I get the same errors off of my backups, so it must be an issue that's been around for awhile.

Repair: IAM chain for object ID 1268915592, index ID 1, partition ID 72057597531455488, alloc unit ID 72057597595287552 (type In-row data), has been truncated before page (1:612342) and will be rebuilt.
Repair: IAM chain for object ID 1268915592, index ID 2, partition ID 72057597531521024, alloc unit ID 72057597595353088 (type In-row data), has been truncated before page (1:544268) and will be rebuilt.
Repair: IAM chain for object ID 1268915592, index ID 3, partition ID 72057597531586560, alloc unit ID 72057597595418624 (type In-row data), has been truncated before page (1:678756) and will be rebuilt.
Repair: IAM chain for object ID 1268915592, index ID 4, partition ID 72057597531652096, alloc unit ID 72057597595484160 (type In-row data), has been truncated before page (1:688003) and will be rebuilt.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:612342) in object ID 1268915592, index ID 1, partition ID 72057597531455488, alloc unit ID 72057597595287552 (type In-row data), but it was not detected in the scan.
        The error has been repaired.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:544268) in object ID 1268915592, index ID 2, partition ID 72057597531521024, alloc unit ID 72057597595353088 (type In-row data), but it was not detected in the scan.
        The error has been repaired.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:678756) in object ID 1268915592, index ID 3, partition ID 72057597531586560, alloc unit ID 72057597595418624 (type In-row data), but it was not detected in the scan.
        The error has been repaired.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:688003) in object ID 1268915592, index ID 4, partition ID 72057597531652096, alloc unit ID 72057597595484160 (type In-row data), but it was not detected in the scan.
        The error has been repaired.
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object ID 1268915592)' (object ID 1268915592).
CHECKDB fixed 4 allocation errors and 0 consistency errors in table '(Object ID 1268915592)' (object ID 1268915592).
CHECKDB found 4 allocation errors and 0 consistency errors in database 'clarkitbiz'.
CHECKDB fixed 4 allocation errors and 0 consistency errors in database 'clarkitbiz'.

Any ideas?  Thank you!
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 6 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 6 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros