Hi all,I have a SQL database that went to suspect mode after a powerdown failure. Here is what I have done so far:- 1 - The .mdf is 40GB in size, so I had to detach it in order to make a backup copy of the data files and log
- 2 - I had to create a new DB with the same name and file layout (not with the same size, I'm afraid...not enough disk space. Is this critical to a sucessfull attach?)
- 3 - Stopped SQL server, replaced files, started SQL server
- 4 - The DB went to a state apparently even deeper than suspect mode, although I could set it to emergency mode
- 5 - Executed: DBCC CHECKDB(<db name>)
Here is the result:DBCC results for 'WIDGETLOG'.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.DBCC results for 'sys.sysrowsetcolumns'.There are 594 rows in 7 pages for object "sys.sysrowsetcolumns".DBCC results for 'sys.sysrowsets'.There are 90 rows in 1 pages for object "sys.sysrowsets".DBCC results for 'sysallocunits'.There are 105 rows in 2 pages for object "sysallocunits".DBCC results for 'sys.sysfiles1'.There are 3 rows in 1 pages for object "sys.sysfiles1".DBCC results for 'sys.syshobtcolumns'.There are 594 rows in 6 pages for object "sys.syshobtcolumns".DBCC results for 'sys.syshobts'.There are 90 rows in 1 pages for object "sys.syshobts".DBCC results for 'sys.sysftinds'.There are 0 rows in 0 pages for object "sys.sysftinds".DBCC results for 'sys.sysserefs'.There are 105 rows in 1 pages for object "sys.sysserefs".DBCC results for 'sys.sysowners'.There are 24 rows in 1 pages for object "sys.sysowners".DBCC results for 'sys.sysprivs'.There are 144 rows in 1 pages for object "sys.sysprivs".DBCC results for 'sys.sysschobjs'.There are 80 rows in 2 pages for object "sys.sysschobjs".DBCC results for 'sys.syscolpars'.There are 514 rows in 11 pages for object "sys.syscolpars".DBCC results for 'sys.sysnsobjs'.There are 1 rows in 1 pages for object "sys.sysnsobjs".DBCC results for 'sys.syscerts'.There are 0 rows in 0 pages for object "sys.syscerts".DBCC results for 'sys.sysxprops'.There are 9 rows in 1 pages for object "sys.sysxprops".DBCC results for 'sys.sysscalartypes'.There are 27 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 186 rows in 4 pages for object "sys.sysidxstats".DBCC results for 'sys.sysiscols'.There are 298 rows in 2 pages for object "sys.sysiscols".DBCC results for 'sys.sysbinobjs'.There are 23 rows in 1 pages for object "sys.sysbinobjs".DBCC results for 'sys.sysobjvalues'.There are 204 rows in 49 pages for object "sys.sysobjvalues".DBCC results for 'sys.sysclsobjs'.There are 15 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 144 rows in 1 pages for object "sys.syssingleobjrefs".DBCC results for 'sys.sysmultiobjrefs'.There are 200 rows in 1 pages for object "sys.sysmultiobjrefs".DBCC results for 'sys.sysdbfiles'.There are 3 rows in 1 pages for object "sys.sysdbfiles".DBCC results for 'sys.sysguidrefs'.There are 0 rows in 0 pages for object "sys.sysguidrefs".DBCC results for 'sys.sysqnames'.There are 91 rows in 1 pages for object "sys.sysqnames".DBCC results for 'sys.sysxmlcomponent'.There are 93 rows in 1 pages for object "sys.sysxmlcomponent".DBCC results for 'sys.sysxmlfacet'.There are 97 rows in 1 pages for object "sys.sysxmlfacet".DBCC results for 'sys.sysxmlplacement'.There are 17 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 0 rows in 0 pages for object "sys.sysbinsubobjs".DBCC results for 'REF_DATE'.There are 464 rows in 1 pages for object "REF_DATE".DBCC results for 'FAC_LOG_TYPE'.There are 57 rows in 1 pages for object "FAC_LOG_TYPE".DBCC results for 'FAC_UTIL_SESSION'.There are 15015061 rows in 197244 pages for object "FAC_UTIL_SESSION".DBCC results for 'FAC_UTIL_WIDGET'.There are 25537479 rows in 257203 pages for object "FAC_UTIL_WIDGET".DBCC results for 'sysdiagrams'.There are 0 rows in 0 pages for object "sysdiagrams".DBCC results for 'sys.queue_messages_1977058079'.There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".DBCC results for 'sys.queue_messages_2009058193'.There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".DBCC results for 'sys.queue_messages_2041058307'.There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".DBCC results for 'FAC_LOG_URL'.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data): Page (1:5413460) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data), page (1:5413460). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data): Page (1:5421158) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data), page (1:5421158). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data): Page (1:5423408) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data), page (1:5423408). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data): Page (1:5426207) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 2073058421, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594049265664 (type In-row data), page (1:5426207). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 6, partition ID 72057594042843136, alloc unit ID 72057594049396736 (type In-row data): Page (1:5191435) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 2073058421, index ID 6, partition ID 72057594042843136, alloc unit ID 72057594049396736 (type In-row data), page (1:5191435). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 7, partition ID 72057594042908672, alloc unit ID 72057594049462272 (type In-row data): Page (1:5413171) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 2073058421, index ID 7, partition ID 72057594042908672, alloc unit ID 72057594049462272 (type In-row data), page (1:5413171). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 7, partition ID 72057594042908672, alloc unit ID 72057594049462272 (type In-row data): Page (1:5413174) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 2073058421, index ID 7, partition ID 72057594042908672, alloc unit ID 72057594049462272 (type In-row data), page (1:5413174). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.There are 49907158 rows in 4175612 pages for object "FAC_LOG_URL".CHECKDB found 0 allocation errors and 14 consistency errors in table 'FAC_LOG_URL' (object ID 2073058421).CHECKDB found 0 allocation errors and 14 consistency errors in database 'WIDGETLOG'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WIDGETLOG).DBCC execution completed. If DBCC printed error messages, contact your system administrator.
According to this, only a repair_allow_data_loss could save something. Should I proceed?I really could use some advices... I am new to this situations.Thank in advance
DBCC CHECKDB result
Posted - 2011-10-10 : 10:56:13
