Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

DBCC - Could not repair this error. Expand / Collapse
Author
Message
Posted Friday, August 31, 2012 1:40 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Sunday, March 30, 2014 8:37 AM
Points: 59, Visits: 144
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?
Post #1353074
Posted Friday, August 31, 2012 2:01 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
Please run the following and post the full and complete output.

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




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1353080
Posted Friday, August 31, 2012 2:12 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Sunday, March 30, 2014 8:37 AM
Points: 59, Visits: 144
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).
Post #1353083
Posted Friday, August 31, 2012 2:31 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
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 2008, MVP
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

Post #1353089
Posted Friday, August 31, 2012 3:13 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, July 17, 2014 11:35 AM
Points: 8, Visits: 40
Did you try re-creating the indexes on the table?
Post #1353100
Posted Friday, August 31, 2012 3:22 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 4:52 PM
Points: 7,079, Visits: 12,569
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
Post #1353104
Posted Friday, August 31, 2012 3:56 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
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 2008, MVP
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

Post #1353109
Posted Monday, September 3, 2012 4:31 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Sunday, March 30, 2014 8:37 AM
Points: 59, Visits: 144
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
Post #1353431
Posted Monday, September 3, 2012 6:21 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 20, 2014 3:50 PM
Points: 28, Visits: 104
re-create indexes for those tables.
Post #1353489
Posted Monday, September 3, 2012 7:07 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
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 2008, MVP
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

Post #1353501
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse