Skip to main content
Solved

DBCC CHECKDB error in Software Factory database

  • October 11, 2019
  • 4 replies
  • 257 views
Hugo Nienhuis
Superhero
Forum|alt.badge.img+12
I performed a DBCC CHECKDB on our databases and it found an error in our SF database:

Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 349973069, index ID 1, partition ID 72057598823759872, alloc unit ID 72057598842699776 (type In-row data) contain allocations for the same interval. IAM pages (1:396048) and (1:292862).
CHECKDB found 1 allocation errors and 0 consistency errors in table 'linked_project' (object ID 349973069).
CHECKDB found 1 allocation errors and 0 consistency errors in database 'DB_software_factory'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DB_software_factory).

I have no clean backup and the DBCC is not able to repair the error.

I can do a clean install of the SF, but I will need to export/import the projects. Is this possible? Are there other solutions, like replacing the 'linked_project' table?

Best answer by Anne Buit

Hi Hugo,

Without delving deeper into the problem, the easiest way to deal with this is probably to export as much data as possible from the linked_project table. Disable all triggers, constraints and foreign keys, truncate the table and re-insert the exported data.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

4 replies

Anne Buit
Community Manager
Forum|alt.badge.img+5
  • Anne Buit
  • Community Manager
  • 637 replies
  • October 11, 2019
Hi Hugo,

Can you create a back-up of the database and run:
code:
DBCC CHECKDB(DB_software_factory, REPAIR_ALLOW_DATA_LOSS);

Afterwards, please check the base projects for your work projects. If they are empty or some are missing, they might have to be re-added manually.
Hugo Nienhuis
Superhero
Forum|alt.badge.img+12
  • Hugo NienhuisSuperhero
  • Author
  • Superhero
  • 136 replies
  • October 11, 2019
I have already done so, resulting in a could not repair this error, see below. There is no data missing in the table.

Repair: IAM chain for object ID 349973069, index ID 1, partition ID 72057598823759872, alloc unit ID 72057598842699776 (type In-row data), has been truncated before page (1:396048) and will be rebuilt.
Msg 8947, Level 16, State 1, Line 1
Table error: Multiple IAM pages for object ID 349973069, index ID 1, partition ID 72057598823759872, alloc unit ID 72057598842699776 (type In-row data) contain allocations for the same interval. IAM pages (1:396048) and (1:292862).
Could not repair this error.
Msg 8969, Level 16, State 2, Line 1
Table error: IAM chain linkage error: Object ID 349973069, index ID 1, partition ID 72057598823759872, alloc unit ID 72057598842699776 (type In-row data). The next page for IAM page (1:292862) is (1:396048), but the previous link for page (1:396048) is (0:0).
Anne Buit
Community Manager
Forum|alt.badge.img+5
  • Anne Buit
  • Community Manager
  • 637 replies
  • Answer
  • October 15, 2019

Hi Hugo,

Without delving deeper into the problem, the easiest way to deal with this is probably to export as much data as possible from the linked_project table. Disable all triggers, constraints and foreign keys, truncate the table and re-insert the exported data.

Hugo Nienhuis
Superhero
Forum|alt.badge.img+12
  • Hugo NienhuisSuperhero
  • Author
  • Superhero
  • 136 replies
  • January 21, 2020

Hi,

 

I finally managed to free up some time to repair the sf database. I succesfully recreated the linked_project table and the DBCC comes back error-free :-)

 

However, how do i know which related baseprojects I should have? Is there a complete list of baseprojects?

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings