April 10, 2016 at 5:43 pm
Can anyone give me a suggested direction to fix these errors?
DBCC CHECKDB('CPS') WITH NO_INFOMSGS, ALL_ERRORMSGS
Msg 8905, Level 16, State 1, Line 1
Extent (1:92720) in database ID 6 is marked allocated in the GAM, but no SGAM or IAM has allocated it.
CHECKDB found 1 allocation errors and 0 consistency errors not associated with any single object.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 141243558, index ID 1, partition ID 72057594252230656, alloc unit ID 72057594291421184 (type In-row data). Page (1:92491) is missing a reference from previous page (1:106656). Possible chain linkage problem.
Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 141243558, index ID 1, partition ID 72057594252230656, alloc unit ID 72057594291421184 (type In-row data). The previous link (1:106656) on page (1:106657) does not match the previous page (1:92491) that the parent (1:10897), slot 389 expects for this page.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'Main' (object ID 141243558).
Msg 8928, Level 16, State 1, Line 1
Object ID 1853249657, index ID 3, partition ID 72057594254131200, alloc unit ID 72057594293846016 (type In-row data): Page (1:104608) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1853249657, index ID 3, partition ID 72057594254131200, alloc unit ID 72057594293846016 (type In-row data), page (1:104608). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1853249657, index ID 3, partition ID 72057594254131200, alloc unit ID 72057594293846016 (type In-row data). Page (1:104608) was not seen in the scan although its parent (1:25627) and previous (1:29276) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1853249657, index ID 3, partition ID 72057594254131200, alloc unit ID 72057594293846016 (type In-row data). Page (1:118398) is missing a reference from previous page (1:104608). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'Paid' (object ID 1853249657).
CHECKDB found 1 allocation errors and 6 consistency errors in database 'CPS'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (CPS).
April 11, 2016 at 2:39 am
Do you have a clean backup and an unbroken chain of log backups since that full backup?
Repair's going to throw away at least one page of table Paid, as far as I can tell.
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
April 13, 2016 at 12:18 pm
Thanks.
I had a backup from 3 days earlier. I chose to repair the db with data loss. I then restored the backup and found 2 payments that were in the backup that were not in the repaired db. I recreated those payment.
My backups quit running when the db corrupted, but I did not receive a notification.
September 28, 2018 at 3:28 am
Lj Burrows - Thursday, September 27, 2018 11:07 PMDBCC CECKDB can't repair these errors. You have got no choice but to restore from backups or extract as much into new database.
Wrong.
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
December 10, 2018 at 9:51 am
This was removed by the editor as SPAM
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply