SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Data corruption (Errors 8905, 8998, 8909, 8906)
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

joefox97
Starting Member

USA
2 Posts

Posted - 10/29/2008 :  11:20:16  Show Profile  Send joefox97 an AOL message  Click to see joefox97's MSN Messenger address  Reply with Quote
So... just by the title, you can tell there's some messed up data going on here.

Here's the results of

DBCC CHECKDB (CSL_OD, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS

I've tried all the various REPAIR options to no avail, and have no backup that's valid. As others have expressed, the end user doesn't see any problems using the database -- but we're not able to create backups of this database, which is why we're trying to fix it. This is a sales/testing database, and it took a while to build it up to where it is. It's been corrupt for at least a year, and nothing we've been able to do has been able to help.

I know the first thought will be hardware (and it probably was at some point) -- but the server it's on now shouldn't have the same problems (we've run disk analysis and it checks out okay).

Here's the results... appreciate any thoughts from you brilliant folks!

Joe

Msg 8905, Level 16, State 1, Line 1
Extent (7:384) in database ID 7 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 1
Extent (7:456) in database ID 7 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 1
Extent (7:560) in database ID 7 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 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (53:0) to (53:8087). See other errors for cause.
Repairing this error requires other errors to be corrected first.
Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 7 pages from (53:0) to (53:517631). See other errors for cause.
Repairing this error requires other errors to be corrected first.

Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page ID (53:1) contains an incorrect page ID in its page header. The PageId in the page header = (61:1).
The system cannot self repair this error.

Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page ID (53:1) contains an incorrect page ID in its page header. The PageId in the page header = (61:1).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page ID (53:1) contains an incorrect page ID in its page header. The PageId in the page header = (61:1).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page ID (53:3) contains an incorrect page ID in its page header. The PageId in the page header = (61:3).
Repairing this error requires other errors to be corrected first.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281474983198720 (type Unknown), page ID (53:6) contains an incorrect page ID in its page header. The PageId in the page header = (61:6).
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:285) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:287) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
CHECKDB found 12 allocation errors and 0 consistency errors not associated with any single object.
Msg 8906, Level 16, State 1, Line 1
Page (7:303) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:312) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:313) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:314) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:329) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:335) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.
Msg 8906, Level 16, State 1, Line 1
Page (7:360) in database ID 7 is allocated in the SGAM (7:3) and PFS (7:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Repairing this error requires other errors to be corrected first.

CHECKDB found 7 allocation errors and 0 consistency errors in table 'CSL_FAM_FAMILY_CONTACT' (object ID 1842105603).
CHECKDB found 19 allocation errors and 0 consistency errors in database 'CSL_OD'.


THANKS!

tosscrosby
Aged Yak Warrior

USA
676 Posts

Posted - 10/29/2008 :  17:11:29  Show Profile  Reply with Quote
While I'm not a corruption expert, I know what the first reply will be: Do you have a good, recent backup? Did you check your event logs on the server to see if any I/O issues are, or have been, occuring? Gail and Paul, among others, can provide more assistance than I (SGAM/IAM errors are a little beyond me at this point) but I know these'll be the first things they'll ask you.

Edit - Sorry, reread your post and you state that this server doesn't have any issues with disk. How did you create this database, from a backup on a different server (that was having I/O issues) and which was already corrupted?

Terry

Edited by - tosscrosby on 10/29/2008 17:15:06
Go to Top of Page

paulrandal
Yak with Vast SQL Skills

USA
899 Posts

Posted - 10/29/2008 :  22:54:54  Show Profile  Visit paulrandal's Homepage  Reply with Quote
DBCC CHECKDB can't repair these errors - as the output from repair states ("The system cannot self repair this error"). You've got no choice here but to restore from backups or extract as much data as your can into a new database.

At this stage, you should bite the bullet and create a new database with as much extracted info as possible as you'e not going to be able to do anything with this corrupt one.

Thanks

Paul Randal
SQL Server MVP, Managing Director, SQLskills.com
Go to Top of Page

joefox97
Starting Member

USA
2 Posts

Posted - 10/29/2008 :  23:52:19  Show Profile  Send joefox97 an AOL message  Click to see joefox97's MSN Messenger address  Reply with Quote
I knew Paul would have the answer... and unforunately, no good backup exists, since this box was a testing environment... live and learn, right? :-)

Thanks for all the replies. Kudos' all the way around!
Go to Top of Page

Lincolnburrows
Starting Member

34 Posts

Posted - 08/08/2014 :  07:00:36  Show Profile  Reply with Quote
DBCC CHECKDB command determined the consistency of SQL database pages, index, and columns physically or logically. But whenever he finds large corruption suddenly the command generate consistency error. So in that case the use of external software is very convenient to perform recovery and error removal.
Go to Top of Page

prett
Posting Yak Master

USA
202 Posts

Posted - 08/13/2014 :  01:51:03  Show Profile  Visit prett's Homepage  Reply with Quote
quote:
Originally posted by Lincolnburrows

DBCC CHECKDB command determined the consistency of SQL database pages, index, and columns physically or logically. But whenever he finds large corruption suddenly the command generate consistency error. So in that case the use of external software is very convenient to perform recovery and error removal.



Good reply on almost 6 years old post...
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.17 seconds. Powered By: Snitz Forums 2000