SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


DBCC - Could not repair this error.


DBCC - Could not repair this error.

Author
Message
sqlmate
sqlmate
SSC-Enthusiastic
SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)

Group: General Forum Members
Points: 144 Visits: 145
Hi guys,
one of my customer's hard drive failed. They were able to safe most of the data and create bit copy of the failed disk but few corrupted sectors were at MDF file. And guess what ... 'we have no backups'. So I run DBCC checkdb and it reported corruption of clustered index, tried to run dbcc checktable (alldocs,repair_allow_data_loss) and got this


DBCC results for 'AllDocs'.
Repair: The Nonclustered index successfully rebuilt for the object "dbo.AllDocs, Docs_IdLevelUnique" in database "WSS_Content_04a315e0-42c4-40d5-a432-65590fe560b0".
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 69575286, index ID 1 will be rebuilt.
Could not repair this error.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 69575286, index ID 1, partition ID 72057608226996224, alloc unit ID 72057608630173696 (type In-row data). Page (1:2728879) was not seen in the scan although its parent (1:2723806) and previous (1:2728878) refer to it. Check any previous errors.
The error has been repaired.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 69575286, index ID 1, partition ID 72057608226996224, alloc unit ID 72057608630173696 (type In-row data). Page (1:2728896) is missing a reference from previous page (1:2728879). Possible chain linkage problem.
The error has been repaired.
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 69575286, index ID 2 will be rebuilt.
The error has been repaired.
There are 51682 rows in 3233 pages for object "AllDocs".
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'AllDocs' (object ID 69575286).
CHECKTABLE fixed 0 allocation errors and 2 consistency errors in table 'AllDocs' (object ID 69575286).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.


I think I ran out of options ... any thoughts? w00t
GilaMonster
GilaMonster
SSC Guru
SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)

Group: General Forum Members
Points: 365679 Visits: 46933
Please run the following and post the full and complete output.


DBCC CHECKDB (<Database Name>Wink WITH NO_INFOMSGS, ALL_ERRORMSGS



Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


sqlmate
sqlmate
SSC-Enthusiastic
SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)

Group: General Forum Members
Points: 144 Visits: 145
Thank you for your help, here you are:


Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:102602) in object ID 0, index ID -1, partition ID 0, alloc unit ID 72057608649768960 (type Unknown), but it was not detected in the scan.
CHECKDB found 1 allocation errors and 0 consistency errors not associated with any single object.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 69575286, index ID 1, partition ID 72057608226996224, alloc unit ID 72057608630173696 (type In-row data). Page (1:2728879) was not seen in the scan although its parent (1:2723806) and previous (1:2728878) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 69575286, index ID 1, partition ID 72057608226996224, alloc unit ID 72057608630173696 (type In-row data). Page (1:2728896) is missing a reference from previous page (1:2728879). Possible chain linkage problem.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:1293) in object ID 69575286, index ID 1, partition ID 72057608245936128, alloc unit ID 72057594043760640 (type LOB data), but it was not detected in the scan.
CHECKDB found 1 allocation errors and 2 consistency errors in table 'AllDocs' (object ID 69575286).
CHECKDB found 2 allocation errors and 2 consistency errors in database 'WSS_Content_04a315e0-42c4-40d5-a432-65590fe560b0'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WSS_Content_04a315e0-42c4-40d5-a432-65590fe560b0).
GilaMonster
GilaMonster
SSC Guru
SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)

Group: General Forum Members
Points: 365679 Visits: 46933
Hell, a sharepoint DB...
Because of the way sharepoint stores the structure of the site in the tables, repairing a sharepoint DB with repair_allow_data_loss can result in an unusable site.

You did take a backup before starting to repair?
I'd honestly suggest restore that pre-repair backup, see if sharepoint will load and then export any and all libraries from sharepoint that will export and then recreate the site.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Nalini D
Nalini D
SSC-Enthusiastic
SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)SSC-Enthusiastic (104 reputation)

Group: General Forum Members
Points: 104 Visits: 43
Did you try re-creating the indexes on the table?
Orlando Colamatteo
Orlando Colamatteo
SSC Guru
SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)

Group: General Forum Members
Points: 68610 Visits: 14491
Are you thinking of a nonclustered index? I think index ID 1 means it is the clustered index, i.e. the actual pages making up the table so the only way to recover from that is to restore from backup or do a repair with data loss, but that may invalidate the database from SharePoint's perspective as Gail has said.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
GilaMonster
GilaMonster
SSC Guru
SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)

Group: General Forum Members
Points: 365679 Visits: 46933
Nalini D (8/31/2012)
Did you try re-creating the indexes on the table?


Won't work. The repair fixed the damage to the nonclustered index and some damage to the clustered index, but the remaining is also in the clustered index. There's no duplicate copy of the data to work from.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


sqlmate
sqlmate
SSC-Enthusiastic
SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)SSC-Enthusiastic (144 reputation)

Group: General Forum Members
Points: 144 Visits: 145
Thanks everybody for their time.

Luckily with my colleague (SharePoint geek) we were able to salvage document streams, their name, path and version... Well it costs us many hours of work which would not be necessary JUST if there would be water-tight backup. (There were NONE!) MDF had +/- 20GB, LDF 300 GB so guess what ...

Do backup, monitor backup, verify backup .. easy ;-)
arunkumarco
arunkumarco
Valued Member
Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)Valued Member (72 reputation)

Group: General Forum Members
Points: 72 Visits: 104
re-create indexes for those tables.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)SSC Guru (365K reputation)

Group: General Forum Members
Points: 365679 Visits: 46933
arunkumarco (9/3/2012)
re-create indexes for those tables.


GilaMonster (8/31/2012)
Nalini D (8/31/2012)
Did you try re-creating the indexes on the table?


Won't work. The repair fixed the damage to the nonclustered index and some damage to the clustered index, but the remaining is also in the clustered index. There's no duplicate copy of the data to work from.


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search