1

We did a disk expansion for VM DB server. However, after this operation the DB became suspect mode and cannot be open.

Then we tried somethings like that;

https://www.sqlrecoverysoftware.net/blog/repair-database-from-suspect-mode.html

But in first checkdb step got following result;

Msg 7987, Level 16, State 1, Line 1
System table pre-checks: Object ID 3 has chain linkage mismatch. (1:13853247)->next = (1:446), but (1:446)->prev = (1:17209791). Check statement terminated due to unrepairable error.
DBCC results for 'myDB'.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'MyDB'.

Also we bought some data recovery tools but it can transfer some of the data, not all of them.

Are there any suggestions?

0

The repair is unrepairable (linkage issue in system table), so you would need to restore it from a good known backup to a point in time (provided the DB is in full recovery and you were taking log backups) you did the disk expansion.

You can try repair allow data loss as last resort.

  • Actually, I accept data loss. But CHECKDB or CHECKDB with REPAIR_ALLOW_DATA_LOSS does not work. It gives me the error I shared. And unfortunately no backup! I can read the wrong page with the following command; DBCC Traceon (3604) DBCC Page ('myDB',1,17209791,3) Is it possible to correct the link manually? – Fatih Nov 11 '18 at 1:42

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.