Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL (Archived)

Database Corruption - Msg 8905 Restore from Backup not an option

Posted on by 635

Hello,

We recently experienced an issue with our database that was caught after the month was closed. So a restore from previous backup is not an option at this point.

When we run DBCC CHECKDB, we get the below errors.

Msg 8905, Level 16, State 1, Line 2

Extent (1:5994432) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Could not repair this error.

Msg 8905, Level 16, State 1, Line 2

Extent (1:5995248) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:5995264) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:5996632) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:5997072) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6107696) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6107784) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6107808) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6108264) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6108800) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6109112) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6109184) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6109216) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6109296) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6109360) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6109408) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

Msg 8905, Level 16, State 1, Line 2

Extent (1:6109488) in database ID 8 is marked allocated in the GAM, but no SGAM or IAM has allocated it.

Repairing this error requires other errors to be corrected first.

17 allocation errors are found, and when the repair with data loss is run the errors are not corrected.

DBCC CHECKDB(Raytheon, repair_allow_data_loss)

WITH NO_INFOMSGS;

Has anyone run into this issue before and was able to correct it without restoring the database?

 

Currently we are running Dynamics 2011 SP2 FP1, SQL2008 R2.

 

Thanks

DBCC CHECKDB

*This post is locked for comments

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans