December 21, 2016 at 12:57 pm
Hi I am looking for some expertise to point me in the right direction. Last night one of application databases threw a 824 error. When I ran DBCC checkdb it identified about 135 inconsistencies which I also identified in the suspect pages table. From what I read, the best way to address this is to restore from last back up that did not have these errors but the problem is I am not sure when that was.
Unfortunately my SQL skills/knowledge are minimal at best, I was not running regular checkdb to verify the consistency of the database so I have no idea how long they have existed. I am hoping to get some solid advice as to the best way to proceed. My tentative plan was to get up a Vm test SQL server that I can restore the DB to and then see if the consistency error is in there as well. I then thought I could run the checkdb with the REPAIR_ALLOW_DATA_LOSS to see what happens?
I saw some people say the 824 error indicates some sort of hardware problem but I am seeing no errors reported from the OS level or hardware diags. I did turn on the CHECKSUM Page Verify option since I discovered the problem.
Any help would be greatly appreciated, thanks!
Here is the output from my checkdb:
DBCC results for 'ContentCentral'.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:9245662) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:9245663) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -9175962193620434944 (type Unknown), page (1:9245664). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7854388802382921728 (type Unknown), page (29697:1888320249). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -14.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 4323574391391059968 (type Unknown), page (12801:579677946). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -14.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -4467443285143126016 (type Unknown), page (17921:1015905787). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7205868257085423616 (type Unknown), page (27905:1972198908). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -12.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 5692670877336272896 (type Unknown), page (24833:1452094461). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7151269232194682880 (type Unknown), page (1:9246184). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7305683300121903104 (type Unknown), page (309:340390894). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7228617693313892352 (type Unknown), page (21059:155816179). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -12.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 4771981856598917120 (type Unknown), page (23910:1936046800). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 7797138583271112704 (type Unknown), page (60:5557243). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 8217491780412768256 (type Unknown), page ID (1:9246189) contains an incorrect page ID in its page header. The PageId in the page header = (27694:1635425677).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:9246462) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:9246463) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 28147914289577984 (type Unknown), page ID (1:9246662) contains an incorrect page ID in its page header. The PageId in the page header = (54:3670117).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 9007336700903424 (type Unknown), page ID (1:9246663) contains an incorrect page ID in its page header. The PageId in the page header = (107:6488165).
Msg 8939, Level 16, State 5, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281475069116416 (type Unknown), page (1:9247024). Test (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281475069116416 (type Unknown), page ID (1:9247025) contains an incorrect page ID in its page header. The PageId in the page header = (0:117520).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281475069116416 (type Unknown), page ID (1:9247026) contains an incorrect page ID in its page header. The PageId in the page header = (0:117520).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281475069116416 (type Unknown), page ID (1:9247027) contains an incorrect page ID in its page header. The PageId in the page header = (0:117520).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281475069116416 (type Unknown), page ID (1:9247028) contains an incorrect page ID in its page header. The PageId in the page header = (0:117520).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 281475069116416 (type Unknown), page ID (1:9247029) contains an incorrect page ID in its page header. The PageId in the page header = (0:117520).
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.
CHECKDB found 0 allocation errors and 24 consistency errors not associated with any single object.
DBCC results for 'sys.sysrscols'.
There are 2692 rows in 31 pages for object "sys.sysrscols".
DBCC results for 'sys.sysrowsets'.
There are 572 rows in 8 pages for object "sys.sysrowsets".
DBCC results for 'sys.sysclones'.
There are 0 rows in 0 pages for object "sys.sysclones".
DBCC results for 'sys.sysallocunits'.
There are 641 rows in 15 pages for object "sys.sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.sysseobjvalues'.
There are 0 rows in 0 pages for object "sys.sysseobjvalues".
DBCC results for 'sys.syspriorities'.
There are 0 rows in 0 pages for object "sys.syspriorities".
DBCC results for 'sys.sysdbfrag'.
There are 0 rows in 0 pages for object "sys.sysdbfrag".
DBCC results for 'sys.sysfgfrag'.
There are 0 rows in 0 pages for object "sys.sysfgfrag".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.syspru'.
There are 0 rows in 0 pages for object "sys.syspru".
DBCC results for 'sys.sysbrickfiles'.
There are 0 rows in 0 pages for object "sys.sysbrickfiles".
DBCC results for 'sys.sysphfg'.
There are 1 rows in 1 pages for object "sys.sysphfg".
DBCC results for 'sys.sysprufiles'.
There are 2 rows in 1 pages for object "sys.sysprufiles".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysowners'.
There are 22 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysdbreg'.
There are 0 rows in 0 pages for object "sys.sysdbreg".
DBCC results for 'sys.sysprivs'.
There are 146 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 3536 rows in 63 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 1928 rows in 36 pages for object "sys.syscolpars".
DBCC results for 'sys.sysxlgns'.
There are 0 rows in 0 pages for object "sys.sysxlgns".
DBCC results for 'sys.sysxsrvs'.
There are 0 rows in 0 pages for object "sys.sysxsrvs".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.sysusermsgs'.
There are 0 rows in 0 pages for object "sys.sysusermsgs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysrmtlgns'.
There are 0 rows in 0 pages for object "sys.sysrmtlgns".
DBCC results for 'sys.syslnklgns'.
There are 0 rows in 0 pages for object "sys.syslnklgns".
DBCC results for 'sys.sysxprops'.
There are 5 rows in 3 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 34 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 884 rows in 20 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 1124 rows in 7 pages for object "sys.sysiscols".
DBCC results for 'sys.sysendpts'.
There are 0 rows in 0 pages for object "sys.sysendpts".
DBCC results for 'sys.syswebmethods'.
There are 0 rows in 0 pages for object "sys.syswebmethods".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysaudacts'.
There are 0 rows in 0 pages for object "sys.sysaudacts".
DBCC results for 'sys.sysobjvalues'.
There are 1660 rows in 316 pages for object "sys.sysobjvalues".
DBCC results for 'sys.syscscolsegments'.
There are 0 rows in 0 pages for object "sys.syscscolsegments".
DBCC results for 'sys.syscsdictionaries'.
There are 0 rows in 0 pages for object "sys.syscsdictionaries".
DBCC results for 'sys.sysclsobjs'.
There are 16 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 1189 rows in 6 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 464 rows in 3 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysfoqueues'.
There are 0 rows in 0 pages for object "sys.sysfoqueues".
DBCC results for 'sys.syschildinsts'.
There are 0 rows in 0 pages for object "sys.syschildinsts".
DBCC results for 'sys.syscompfragments'.
There are 0 rows in 0 pages for object "sys.syscompfragments".
DBCC results for 'sys.sysftsemanticsdb'.
There are 0 rows in 0 pages for object "sys.sysftsemanticsdb".
DBCC results for 'sys.sysftstops'.
There are 0 rows in 0 pages for object "sys.sysftstops".
DBCC results for 'sys.sysftproperties'.
There are 0 rows in 0 pages for object "sys.sysftproperties".
DBCC results for 'sys.sysxmitbody'.
There are 0 rows in 0 pages for object "sys.sysxmitbody".
DBCC results for 'sys.sysfos'.
There are 0 rows in 0 pages for object "sys.sysfos".
DBCC results for 'sys.sysqnames'.
There are 98 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 100 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 112 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 19 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 3 rows in 1 pages for object "sys.sysbinsubobjs".
DBCC results for 'sys.syssoftobjrefs'.
There are 60 rows in 1 pages for object "sys.syssoftobjrefs".
DBCC results for 'WorkflowActionGroup'.
There are 6 rows in 1 pages for object "WorkflowActionGroup".
DBCC results for 'DocTypeFieldExternalLookupItem'.
There are 0 rows in 0 pages for object "DocTypeFieldExternalLookupItem".
DBCC results for 'UserMenuItem'.
There are 0 rows in 0 pages for object "UserMenuItem".
DBCC results for 'DocTypeDefaultUserSearchResultField'.
There are 34139 rows in 404 pages for object "DocTypeDefaultUserSearchResultField".
DBCC results for 'DragDrop'.
There are 388 rows in 41 pages for object "DragDrop".
DBCC results for 'FolderPropertiesSession'.
There are 1 rows in 1 pages for object "FolderPropertiesSession".
DBCC results for 'DocTypeDefaultUserSearchField'.
There are 30319 rows in 287 pages for object "DocTypeDefaultUserSearchField".
DBCC results for 'LogEntry'.
There are 1366252 rows in 77027 pages for object "LogEntry".
DBCC results for 'PdfHits'.
There are 0 rows in 1 pages for object "PdfHits".
DBCC results for 'DocTypeDefaultAdminSearchResultField'.
There are 895 rows in 7 pages for object "DocTypeDefaultAdminSearchResultField".
DBCC results for 'Log'.
There are 2765 rows in 330 pages for object "Log".
DBCC results for 'DocTypeDefaultAdminSearchField'.
There are 803 rows in 6 pages for object "DocTypeDefaultAdminSearchField".
DBCC results for 'WorkflowTriggerUser'.
There are 0 rows in 0 pages for object "WorkflowTriggerUser".
DBCC results for 'DocTypeCaptureFormData'.
There are 105 rows in 1 pages for object "DocTypeCaptureFormData".
DBCC results for 'WorkflowActionUser'.
There are 0 rows in 0 pages for object "WorkflowActionUser".
DBCC results for 'DocTypeFolderBuildItem'.
There are 1331 rows in 20 pages for object "DocTypeFolderBuildItem".
DBCC results for 'WorkflowRuleTrigger'.
There are 386 rows in 4 pages for object "WorkflowRuleTrigger".
DBCC results for 'DocTypeFileBuildItem'.
There are 110 rows in 2 pages for object "DocTypeFileBuildItem".
DBCC results for 'Document'.
There are 9838594 rows in 153411 pages for object "Document".
DBCC results for 'Catalog'.
There are 10 rows in 1 pages for object "Catalog".
DBCC results for 'DocumentVersionFile_CB'.
There are 10002741 rows in 739079 pages for object "DocumentVersionFile_CB".
DBCC results for 'DocTypeFieldSpentNumericValue'.
There are 0 rows in 0 pages for object "DocTypeFieldSpentNumericValue".
DBCC results for 'ApprovalProcessMember'.
There are 250 rows in 12 pages for object "ApprovalProcessMember".
DBCC results for 'DocType'.
There are 194 rows in 4 pages for object "DocType".
DBCC results for 'ApprovalProcessMemberFieldPermission'.
There are 1615 rows in 16 pages for object "ApprovalProcessMemberFieldPermission".
DBCC results for 'ApprovalProcessCompletion'.
There are 65539 rows in 1533 pages for object "ApprovalProcessCompletion".
DBCC results for 'UserSubstitute'.
There are 0 rows in 0 pages for object "UserSubstitute".
DBCC results for 'ApprovalProcessStep'.
There are 468 rows in 33 pages for object "ApprovalProcessStep".
DBCC results for 'DocTypeField'.
There are 2316 rows in 71 pages for object "DocTypeField".
DBCC results for 'CaptureJob'.
There are 441 rows in 24 pages for object "CaptureJob".
DBCC results for 'ApprovalProcessStepHistory'.
There are 229287 rows in 6523 pages for object "ApprovalProcessStepHistory".
DBCC results for 'CaptureJobInputItem'.
There are 22 rows in 7 pages for object "CaptureJobInputItem".
DBCC results for 'PacketTemplate'.
There are 0 rows in 0 pages for object "PacketTemplate".
DBCC results for 'ApprovalProcessStepCompletion'.
There are 0 rows in 0 pages for object "ApprovalProcessStepCompletion".
DBCC results for 'ExternalApplication'.
There are 0 rows in 0 pages for object "ExternalApplication".
DBCC results for 'CaptureFormSession'.
There are 477314 rows in 4458 pages for object "CaptureFormSession".
DBCC results for 'UIThemeStorage'.
There are 0 rows in 0 pages for object "UIThemeStorage".
DBCC results for 'DirectScan'.
There are 12 rows in 1 pages for object "DirectScan".
DBCC results for 'CategoryLog'.
There are 2765 rows in 9 pages for object "CategoryLog".
DBCC results for 'MessageTemplate'.
There are 195 rows in 30 pages for object "MessageTemplate".
DBCC results for 'DocTypeFieldRecognitionZoneCondition'.
There are 0 rows in 0 pages for object "DocTypeFieldRecognitionZoneCondition".
DBCC results for 'CatalogFolderToCatalog'.
There are 10 rows in 1 pages for object "CatalogFolderToCatalog".
DBCC results for 'DocumentFolder'.
There are 117043 rows in 3737 pages for object "DocumentFolder".
DBCC results for 'DocumentVersionForm'.
There are 244980 rows in 39518 pages for object "DocumentVersionForm".
DBCC results for 'CatalogAdminMembership'.
There are 0 rows in 0 pages for object "CatalogAdminMembership".
DBCC results for 'ExternalDataSource'.
There are 0 rows in 0 pages for object "ExternalDataSource".
DBCC results for 'DocumentVersionFile'.
There are 10002741 rows in 242363 pages for object "DocumentVersionFile".
DBCC results for 'AdminPermission'.
There are 134 rows in 2 pages for object "AdminPermission".
DBCC results for 'DocumentVersionAnnotations'.
There are 164147 rows in 630 pages for object "DocumentVersionAnnotations".
DBCC results for 'DocTypeFieldExternalLookup'.
There are 0 rows in 0 pages for object "DocTypeFieldExternalLookup".
DBCC results for 'PacketCompletion'.
There are 0 rows in 0 pages for object "PacketCompletion".
DBCC results for 'DocumentApprovalProcess'.
There are 0 rows in 0 pages for object "DocumentApprovalProcess".
DBCC results for 'ActiveDirectoryDomain'.
There are 1 rows in 1 pages for object "ActiveDirectoryDomain".
DBCC results for 'PacketTemplateDocType'.
There are 0 rows in 0 pages for object "PacketTemplateDocType".
DBCC results for 'ApprovalProcessStatus'.
There are 65776 rows in 1002 pages for object "ApprovalProcessStatus".
DBCC results for 'User'.
There are 104 rows in 4 pages for object "User".
DBCC results for 'WorkQueueDocument'.
There are 0 rows in 1 pages for object "WorkQueueDocument".
DBCC results for 'DocTypeRetentionPolicy'.
There are 175 rows in 2 pages for object "DocTypeRetentionPolicy".
DBCC results for 'Document_S'.
There are 9838594 rows in 724936 pages for object "Document_S".
DBCC results for 'WorkflowRule'.
There are 311 rows in 11 pages for object "WorkflowRule".
DBCC results for 'WorkQueueDocumentCompletion'.
There are 0 rows in 0 pages for object "WorkQueueDocumentCompletion".
DBCC results for 'DocTypePermission'.
There are 1118 rows in 16 pages for object "DocTypePermission".
DBCC results for 'WorkflowTrigger'.
There are 389 rows in 48 pages for object "WorkflowTrigger".
DBCC results for 'ApprovalProcess'.
There are 65 rows in 4 pages for object "ApprovalProcess".
DBCC results for 'DocumentVersionFullText'.
There are 10002741 rows in 38513 pages for object "DocumentVersionFullText".
DBCC results for 'DocTypeShortLinkSharePermission'.
There are 0 rows in 0 pages for object "DocTypeShortLinkSharePermission".
DBCC results for 'ExportDataPath'.
There are 0 rows in 0 pages for object "ExportDataPath".
DBCC results for 'DocumentVersionThumbnail'.
There are 10002741 rows in 39898 pages for object "DocumentVersionThumbnail".
DBCC results for 'DocumentShortLink'.
There are 0 rows in 0 pages for object "DocumentShortLink".
DBCC results for 'DocumentPath'.
There are 10002741 rows in 828934 pages for object "DocumentPath".
DBCC results for 'ExportDataTemplate'.
There are 0 rows in 0 pages for object "ExportDataTemplate".
DBCC results for 'UIThemeMember'.
There are 0 rows in 0 pages for object "UIThemeMember".
DBCC results for 'CaptureJobSinglePageImageItem'.
There are 22 rows in 4 pages for object "CaptureJobSinglePageImageItem".
DBCC results for 'GroupMembership'.
There are 230 rows in 3 pages for object "GroupMembership".
DBCC results for 'CaptureJobInputItemData'.
There are 22 rows in 2 pages for object "CaptureJobInputItemData".
DBCC results for 'DocTypeCaptureForm'.
There are 105 rows in 3 pages for object "DocTypeCaptureForm".
DBCC results for 'ExportDataElement'.
There are 0 rows in 0 pages for object "ExportDataElement".
DBCC results for 'CaptureJobSinglePageImageItemZonal'.
There are 0 rows in 0 pages for object "CaptureJobSinglePageImageItemZonal".
DBCC results for 'CaptureJobSinglePageImageItemData'.
There are 22 rows in 7 pages for object "CaptureJobSinglePageImageItemData".
DBCC results for 'UserOptions'.
There are 104 rows in 4 pages for object "UserOptions".
DBCC results for 'CaptureStatus'.
There are 1 rows in 1 pages for object "CaptureStatus".
DBCC results for 'UserMessage'.
There are 245466 rows in 48252 pages for object "UserMessage".
DBCC results for 'WorkflowAction'.
There are 320 rows in 37 pages for object "WorkflowAction".
DBCC results for 'UserDefaultDocType'.
There are 559 rows in 7 pages for object "UserDefaultDocType".
DBCC results for 'WorkflowRuleAction'.
There are 311 rows in 3 pages for object "WorkflowRuleAction".
DBCC results for 'DocTypePermission_S'.
There are 8436 rows in 119 pages for object "DocTypePermission_S".
DBCC results for 'ReportTemplate'.
There are 0 rows in 0 pages for object "ReportTemplate".
DBCC results for 'UserAddressBookItem'.
There are 22 rows in 1 pages for object "UserAddressBookItem".
DBCC results for 'ReportColumn'.
There are 0 rows in 0 pages for object "ReportColumn".
DBCC results for 'PostScanDocument'.
There are 216 rows in 23 pages for object "PostScanDocument".
DBCC results for 'ReportFilterCatalog'.
There are 0 rows in 0 pages for object "ReportFilterCatalog".
DBCC results for 'PostScanDocumentThumbnail'.
There are 216 rows in 1 pages for object "PostScanDocumentThumbnail".
DBCC results for 'ReportFilterDocType'.
There are 0 rows in 0 pages for object "ReportFilterDocType".
DBCC results for 'WorkflowRuleCompletion'.
There are 0 rows in 0 pages for object "WorkflowRuleCompletion".
DBCC results for 'ReportFilterDocTypeField'.
There are 0 rows in 0 pages for object "ReportFilterDocTypeField".
DBCC results for 'PostScanDocumentApprovalProcess'.
There are 0 rows in 0 pages for object "PostScanDocumentApprovalProcess".
DBCC results for 'ReportFilterDocTypeFieldMatch'.
There are 0 rows in 0 pages for object "ReportFilterDocTypeFieldMatch".
DBCC results for 'LoginSession'.
There are 747 rows in 16 pages for object "LoginSession".
DBCC results for 'ReportFilterApprovalProcess'.
There are 0 rows in 0 pages for object "ReportFilterApprovalProcess".
DBCC results for 'RememberLogin'.
There are 234 rows in 3 pages for object "RememberLogin".
DBCC results for 'ReportFilterSystemField'.
There are 0 rows in 0 pages for object "ReportFilterSystemField".
DBCC results for 'SavedSearch'.
There are 23 rows in 5 pages for object "SavedSearch".
DBCC results for 'ReportFilterSystemFieldMatch'.
There are 0 rows in 0 pages for object "ReportFilterSystemFieldMatch".
DBCC results for 'ServiceCommand'.
There are 0 rows in 1 pages for object "ServiceCommand".
DBCC results for 'ReportFilterApprovalProcessTimeframe'.
There are 0 rows in 0 pages for object "ReportFilterApprovalProcessTimeframe".
DBCC results for 'RetroFolderFileBuildItem'.
There are 0 rows in 0 pages for object "RetroFolderFileBuildItem".
DBCC results for 'ReportFilterApprovalProcessTimeframeMatch'.
There are 0 rows in 0 pages for object "ReportFilterApprovalProcessTimeframeMatch".
DBCC results for 'PostScanDocumentField'.
There are 1044 rows in 26 pages for object "PostScanDocumentField".
DBCC results for 'ReportFilterWorkQueueArrival'.
There are 0 rows in 0 pages for object "ReportFilterWorkQueueArrival".
DBCC results for 'QCard'.
There are 3480569 rows in 449948 pages for object "QCard".
DBCC results for 'ReportFilterWorkQueueArrivalMatch'.
There are 0 rows in 0 pages for object "ReportFilterWorkQueueArrivalMatch".
DBCC results for 'ReportSegment'.
There are 0 rows in 0 pages for object "ReportSegment".
DBCC results for 'MessageTemplateUser'.
There are 45 rows in 1 pages for object "MessageTemplateUser".
DBCC results for 'ApprovalProcessGroup'.
There are 0 rows in 0 pages for object "ApprovalProcessGroup".
DBCC results for 'MessageTemplateGroup'.
There are 108 rows in 1 pages for object "MessageTemplateGroup".
DBCC results for 'ApprovalProcessGroupMember'.
There are 0 rows in 0 pages for object "ApprovalProcessGroupMember".
DBCC results for 'admLOAValidation'.
There are 1 rows in 1 pages for object "admLOAValidation".
DBCC results for 'CustomMenuItemSource'.
There are 0 rows in 0 pages for object "CustomMenuItemSource".
DBCC results for 'CatalogAdminPermission'.
There are 1 rows in 1 pages for object "CatalogAdminPermission".
DBCC results for 'GridResultsField'.
There are 8626 rows in 217 pages for object "GridResultsField".
DBCC results for 'Category'.
There are 5 rows in 1 pages for object "Category".
DBCC results for 'MakeSearchable'.
There are 0 rows in 0 pages for object "MakeSearchable".
DBCC results for 'CustomMenuItem'.
There are 0 rows in 0 pages for object "CustomMenuItem".
DBCC results for 'WorkflowRulePacketCompletion'.
There are 0 rows in 0 pages for object "WorkflowRulePacketCompletion".
DBCC results for 'ContentDirectorAuthenticationNonce'.
There are 0 rows in 0 pages for object "ContentDirectorAuthenticationNonce".
DBCC results for 'SystemField'.
There are 7 rows in 1 pages for object "SystemField".
DBCC results for 'XmlKeyedSection'.
There are 30 rows in 4 pages for object "XmlKeyedSection".
DBCC results for 'DocumentField'.
There are 56770309 rows in 967879 pages for object "DocumentField".
DBCC results for 'UITheme'.
There are 0 rows in 0 pages for object "UITheme".
DBCC results for 'DocumentCheckedOut'.
There are 7 rows in 1 pages for object "DocumentCheckedOut".
DBCC results for 'DocTypeFieldCurrentNumericValue'.
There are 2316 rows in 12 pages for object "DocTypeFieldCurrentNumericValue".
DBCC results for 'ProductVersion'.
There are 0 rows in 0 pages for object "ProductVersion".
Msg 8944, Level 16, State 12, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9242061), row 1. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 2816 and 1429.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9243984), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 7008 and 547.
Msg 8944, Level 16, State 16, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244664), row 0. Test (VarColOffsets + (int)(sizeof (VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 76099 and 1375.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244665), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 8056 and 1471.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244667), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 7681 and 307.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244668), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 2593 and 449.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244669), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 1936 and 1391.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:2483629) is missing a reference from previous page (1:9242063). Possible chain linkage problem.
Msg 8944, Level 16, State 12, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9242061), row 1. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 2816 and 1429.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9242061) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page ID (1:9242062) contains an incorrect page ID in its page header. The PageId in the page header = (1:9231902).
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9242062) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page ID (1:9242063) contains an incorrect page ID in its page header. The PageId in the page header = (1:9231903).
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9242063) could not be processed. See other errors for details.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9243984), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 7008 and 547.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9243984) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page ID (1:9243985) contains an incorrect page ID in its page header. The PageId in the page header = (1:9229273).
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9243985) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page ID (1:9243986) contains an incorrect page ID in its page header. The PageId in the page header = (1:9229274).
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9243986) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page ID (1:9243987) contains an incorrect page ID in its page header. The PageId in the page header = (1:9229275).
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9243987) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page ID (1:9243988) contains an incorrect page ID in its page header. The PageId in the page header = (1:9229276).
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9243988) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page ID (1:9243989) contains an incorrect page ID in its page header. The PageId in the page header = (1:9229277).
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9243989) could not be processed. See other errors for details.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9242061) was not seen in the scan although its parent (1:955758) and previous (1:9242060) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:955758), slot 148 refers to child page (1:9242062) and previous child (1:9242061), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:955758), slot 149 refers to child page (1:9242063) and previous child (1:9242062), but they were not encountered.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9243984) was not seen in the scan although its parent (1:1617099) and previous (1:9243959) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 111 refers to child page (1:9243985) and previous child (1:9243984), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 112 refers to child page (1:9243986) and previous child (1:9243985), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 113 refers to child page (1:9243987) and previous child (1:9243986), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 114 refers to child page (1:9243988) and previous child (1:9243987), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 115 refers to child page (1:9243989) and previous child (1:9243988), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9243990) is missing a reference from previous page (1:9243989). Possible chain linkage problem.
Msg 8944, Level 16, State 16, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244664), row 0. Test (VarColOffsets + (int)(sizeof (VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 76099 and 1375.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9244664) could not be processed. See other errors for details.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244665), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 8056 and 1471.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9244665) could not be processed. See other errors for details.
Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244666). Test (m_freeCnt == freeCnt) failed. Values are 5218 and 8096.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9244666) could not be processed. See other errors for details.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244667), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 7681 and 307.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9244667) could not be processed. See other errors for details.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244668), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 2593 and 449.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9244668) could not be processed. See other errors for details.
Msg 8944, Level 16, State 13, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9244669), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 1936 and 1391.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9244669) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9245661). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245661) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245662) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245663) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245664) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245665) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245666) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245667) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245668) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9245669) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246184) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246185) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246186) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246187) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246188) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246189) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9246461). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246461) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246462) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246463) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9246661). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246661) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246662) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246663) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data), page (1:9246909). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 133129 and -1.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9246909) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9247024) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9247025) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9247026) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9247027) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9247028) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data): Page (1:9247029) could not be processed. See other errors for details.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9244664) was not seen in the scan although its parent (1:1617099) and previous (1:72598) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 191 refers to child page (1:9244665) and previous child (1:9244664), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 192 refers to child page (1:9244666) and previous child (1:9244665), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 193 refers to child page (1:9244667) and previous child (1:9244666), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 194 refers to child page (1:9244668) and previous child (1:9244667), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617099), slot 195 refers to child page (1:9244669) and previous child (1:9244668), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9244670) is missing a reference from previous page (1:9244669). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9245661) was not seen in the scan although its parent (1:816759) and previous (1:9245660) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 83 refers to child page (1:9245662) and previous child (1:9245661), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 84 refers to child page (1:9245663) and previous child (1:9245662), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 85 refers to child page (1:9245664) and previous child (1:9245663), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 86 refers to child page (1:9245665) and previous child (1:9245664), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 87 refers to child page (1:9245666) and previous child (1:9245665), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 88 refers to child page (1:9245667) and previous child (1:9245666), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 89 refers to child page (1:9245668) and previous child (1:9245667), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 90 refers to child page (1:9245669) and previous child (1:9245668), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9245670) is missing a reference from previous page (1:9245669). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246184) was not seen in the scan although its parent (1:816759) and previous (1:9246127) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 128 refers to child page (1:9246185) and previous child (1:9246184), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 129 refers to child page (1:9246186) and previous child (1:9246185), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 130 refers to child page (1:9246187) and previous child (1:9246186), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 131 refers to child page (1:9246188) and previous child (1:9246187), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 132 refers to child page (1:9246189) and previous child (1:9246188), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246190) is missing a reference from previous page (1:9246189). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246461) was not seen in the scan although its parent (1:816759) and previous (1:9246460) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 161 refers to child page (1:9246462) and previous child (1:9246461), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 162 refers to child page (1:9246463) and previous child (1:9246462), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246488) is missing a reference from previous page (1:9246463). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246661) was not seen in the scan although its parent (1:816759) and previous (1:9246660) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 179 refers to child page (1:9246662) and previous child (1:9246661), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 180 refers to child page (1:9246663) and previous child (1:9246662), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246704) is missing a reference from previous page (1:9246663). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246742) was not seen in the scan although its parent (1:816759) and previous (1:9246741) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:816759), slot 200 refers to child page (1:9246743) and previous child (1:9246742), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246752) is missing a reference from previous page (1:9246743). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246904) was not seen in the scan although its parent (1:1617100) and previous (1:75654) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 5 refers to child page (1:9246905) and previous child (1:9246904), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 6 refers to child page (1:9246906) and previous child (1:9246905), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 7 refers to child page (1:9246907) and previous child (1:9246906), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 8 refers to child page (1:9246908) and previous child (1:9246907), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 9 refers to child page (1:9246909) and previous child (1:9246908), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9246910) is missing a reference from previous page (1:9246909). Possible chain linkage problem.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9247024) was not seen in the scan although its parent (1:1617100) and previous (1:9246959) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 24 refers to child page (1:9247025) and previous child (1:9247024), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 25 refers to child page (1:9247026) and previous child (1:9247025), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 26 refers to child page (1:9247027) and previous child (1:9247026), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 27 refers to child page (1:9247028) and previous child (1:9247027), but they were not encountered.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Index node page (1:1617100), slot 28 refers to child page (1:9247029) and previous child (1:9247028), but they were not encountered.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1986106116, index ID 1, partition ID 72057594281132032, alloc unit ID 72057594303676416 (type In-row data). Page (1:9247030) is missing a reference from previous page (1:9247029). Possible chain linkage problem.
DBCC results for 'DocumentVersion'.
There are 10615087 rows in 1412932 pages for object "DocumentVersion".
CHECKDB found 0 allocation errors and 129 consistency errors in table 'DocumentVersion' (object ID 1986106116).
DBCC results for 'MimeType'.
There are 202 rows in 3 pages for object "MimeType".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'ViewState'.
There are 431 rows in 22 pages for object "ViewState".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'DocumentRetentionPolicy'.
There are 0 rows in 0 pages for object "DocumentRetentionPolicy".
DBCC results for 'Group'.
There are 32 rows in 1 pages for object "Group".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'DocTypeFieldRecognitionZone'.
There are 8 rows in 1 pages for object "DocTypeFieldRecognitionZone".
DBCC results for 'sys.filestream_tombstone_2073058421'.
There are 0 rows in 0 pages for object "sys.filestream_tombstone_2073058421".
DBCC results for 'sys.syscommittab'.
There are 0 rows in 0 pages for object "sys.syscommittab".
DBCC results for 'DocTypeFieldFieldChoices'.
There are 2316 rows in 10 pages for object "DocTypeFieldFieldChoices".
DBCC results for 'WorkflowTriggerGroup'.
There are 0 rows in 0 pages for object "WorkflowTriggerGroup".
DBCC results for 'sys.filetable_updates_2105058535'.
There are 0 rows in 0 pages for object "sys.filetable_updates_2105058535".
DBCC results for 'DocTypeFieldExternalLookupSelectItem'.
There are 0 rows in 0 pages for object "DocTypeFieldExternalLookupSelectItem".
CHECKDB found 0 allocation errors and 153 consistency errors in database 'ContentCentral'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (ContentCentral).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
December 21, 2016 at 1:11 pm
At first glance that looks like some serious issues. As a first try do NOT run repair data loss as you will loose random data within your database and it still may not totally fix the issues. This should ONLY be used as a very last resort and unless it is a test system you boss should know you are going to run something that will loose random data before you do it. First I would do a restore of backups to a different database name and run checkdb on those and see where the corruption started. Next I would contact your server/SAN folks and have them look at that side of things. If that is a live production db you should place a call to MSFT support and they can help you.
December 21, 2016 at 1:18 pm
Yep it's a live, important, production database. So I could restore a renamed copy to the same server without complication? Yep getting credit card out to call MSFT.
December 21, 2016 at 9:18 pm
This was removed by the editor as SPAM
December 22, 2016 at 2:29 am
Tbh, don't bother calling Microsoft. They'll tell you to restore your last good backup. They won't help with data recovery (not allowed to) and probably won't be much more help than we will.
A restored copy of that database will also have the corruption in it.
Few things to start:
What backups do you have? (full backups going back how far, log backups going back how far, etc)
Look in the SQL Server error log, do you see any 824 errors in the log and, if so, how far back.
What's the data loss allowance for this database? How much data can you lose without serious problems?
How critical is the table "DocumentVersion"?
824, 823, 825 are all indicative of IO errors, SQL doesn't corrupt its own databases, most of the time it's related to bad drives, faulty drivers, faulty firmware, etc.
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 22, 2016 at 3:54 am
Have a chat with your storage guys as well as everything else written here. If they haven't picked up on any problems then the question needs to be asked why.
And you might be in just the right place to stop a disaster even if it means losing an amount of data....
How often do you run CHECKDB?
December 22, 2016 at 3:56 am
JasonClark (12/21/2016)
For resolving Error 824, you may have a look on this URL:Basically, it is caused due to any logical inconsistency.
Using Repair_Allow_Data_Loss may cause loss of data and only one must use it at Last resort.
It isn't logical inconsistency...it is likely indicative of an impending hardware failure....
December 22, 2016 at 4:48 am
kevaburg (12/22/2016)
it is likely indicative of an impending hardware failure....
Not necessarily. It could be anything in the IO stack from buggy filter drives to faulty cables, faulty switch, problems with write cache, etc, etc. It's not necessarily failing drives.
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 22, 2016 at 5:20 am
GilaMonster (12/22/2016)
kevaburg (12/22/2016)
it is likely indicative of an impending hardware failure....Not necessarily. It could be anything in the IO stack from buggy filter drives to faulty cables, faulty switch, problems with write cache, etc, etc. It's not necessarily failing drives.
Fair enough....I read it again and realised I misinterpreted it wrongly....
December 22, 2016 at 5:26 am
First off, thanks for all the feedback. Let me try to answer as much as I can.
I was not doing regular DBCHECKS, as I said my SQL background is pretty basic. I did not realize scheduling these was a key to catching corruption early. If I were to guess, I bet this corruption has been in there for awhile. I have since added nightly DBCHECKS that run before the SQL back up.
My back up plan is with a Unitrends appliance, one full a week with differentials the other days. I keep roughly two weeks of back ups.
I did find updated firmware and drivers for the PERC RAID 10 controller which I applied yesterday. (Dell server)
I DID call Microsoft and spent the $499. The guy was VERY helpful and knowledgeable. Let me outline what we did.
Restored the differential from the prior night under a different name and ran a DBCHECK against it. It showed the same inconsistencies as the production database. We then backed up the production database and restored it back to the same server under yet another name. We then ran another DBCHECK on the restored DB with the allow data loss option. It cleared all of the inconsistencies.
The tech then ran some commands that allowed us to see the differences in numbers of records in various tables from the production DB versus the repaired one. He said if I wanted you can actually extract the rows of data from production that are missing from the repaired data and insert them (ran some compare statement to demonstrate) However he said if any of the data has constraints it can get pretty messy pretty quickly.
This is a document imaging application that has millions of images in it. I told him that I was fine with losing a handful of them as long as the application still worked ok. So we took SQL offline and flipped the DB file names around so the restored/repaired DB was now production.
After we brought it back up I went into the app and was able to do a few complete document capture and retrievals and everything seemed fine.
In addition to the regular DB checks I am going to set up additional monitoring including notification if the application log throws any more 823 or 824 errors. It has been quite the learning experience.
The Microsoft tech was very thorough (and not from India!) and was committed to resolving the issue to my satisfaction. Below is his recap of the ticket.
I have included a summary of our troubleshooting below:
•Started LogMeIn screen share.
•Restoring FULL from 12/17 night then DIFF from 12/20 night.
oDBC CHECKDB reported "repair_allow_data_loss" is minimum repair
•Restoring only FULL from 12/17
oDid not restore.
•Copied corrupt database "ContentCentral" and restored it as "ContentCentral12-21-Corrupt” and repaired it using below:
-- run from context of master database
use master
-- put the database into single-user mode
alter database [ContentCentral12-21-Corrupt] set single_user with rollback immediate
-- put the database into emergency mode
alter database [ContentCentral12-21-Corrupt] set emergency
-- perform the repair
dbcc checkdb ([ContentCentral12-21-Corrupt], repair_allow_data_loss)
-- return the database to multi user mode
alter database [ContentCentral12-21-Corrupt] set multi_user
•After the repair the minimum repair level was "repair_allow_data_loss"
• Comparing row counts
use [ContentCentral]
select t.name TableName, i.rows Records
from sysobjects t, sysindexes i
where t.xtype = 'U' and i.id = t.id and i.indid in (0,1)
order by TableName;
use [ContentCentral12-21-Corrupt]
select t.name TableName, i.rows Records
from sysobjects t, sysindexes i
where t.xtype = 'U' and i.id = t.id and i.indid in (0,1)
order by TableName;
•Many tables had different row counts.
•Finding changes
select * from OriginalDB.Schema.Table
where OriginalDB.Schema.Table.IDColumn
not in (select IDColumn from RepairedDB.Schema.Table)
•Running repair again with “repair_allow_data_loss”.
oReporting 0 allocation and 0 consistency errors!
•Stopping the instance to swap repaired MDF and LDF with live production MDF and LDF to test with application
oContentCentral.mdf -> ContentCentral_live-corrupted.mdf
oContentCentral_log.ldf -> ContentCentral_log-live-corrupted.ldf
oContentCentral12-21corrupt.mdf -> ContentCentral.mdf
oContentCentral_log12-21corrupt.ldf -> ContentCentral_log.ldf
•Started SQL, ContentCentral12-21-corrupted is "Recovery pending" - this is expected since the data files for this database were renamed.
•ContentCentral came online.
•Tested successfully from application.
December 22, 2016 at 5:38 am
Many thanks for sharing! My advice about the checkdb though would be this:
It seems like you have a very large database and doing a full CHECKDB every night might lead to performance problems if it runs into the working day.
For that reason, run this once a week on a quiet day.....
DBCC CHECKDB WITH DATA_PURITY, NO_INFOMSGS, ALL_ERRORMSGS
and this daily.........
DBCC CHECKDB WITH PHYSICAL_ONLY, NO_INFOMSGS, ALL_ERRORMSGS
Have you managed to find out what the root cause of the problem was?
December 22, 2016 at 5:55 am
Yea the DB is large, 90 gigs or so. Even with it's size we were completing the checks in less than 25 minutes.
I will look at implementing your suggestion, thanks!!
Oh, as far as the root problem, no I do not know and like I said, I would bet the inconsistencies have been in there for awhile. There was another 824 error in the log from 11/29 that I did not catch.
This has been my first experience with SQL DB corruption, I guess it shows.
December 25, 2016 at 10:37 pm
also take a look at this link, hope this will help you out: http://sqltechtips.blogspot.com/2015/11/troubleshooting-error-824.html
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply