Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

Database Corruption - Msg 8905 Restore from Backup not an option

(0) ShareShare
ReportReport
Posted on by 641

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

#1
Community Member Profile Picture

Community Member 136

#2
Mohamed Amine Mahmoudi Profile Picture

Mohamed Amine Mahmoudi 102 Super User 2025 Season 1

#3
REUser Profile Picture

REUser 8

Featured topics

Product updates

Dynamics 365 release plans