September 4, 2011 at 9:45 am
Dear All,
Could you Please help me if can resolve error below Once execute DBCC CHECKDB Command?Is there anyway to resolve this ?
DBCC results for 'My_Data'.
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.
DBCC results for 'sys.sysrscols'.
There are 638 rows in 8 pages for object "sys.sysrscols".
DBCC results for 'sys.sysrowsets'.
There are 92 rows in 1 pages for object "sys.sysrowsets".
DBCC results for 'sys.sysallocunits'.
There are 104 rows in 2 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.syspriorities'.
There are 0 rows in 0 pages for object "sys.syspriorities".
DBCC results for 'sys.sysfgfrag'.
There are 2 rows in 1 pages for object "sys.sysfgfrag".
DBCC results for 'sys.sysphfg'.
There are 1 rows in 1 pages for object "sys.sysphfg".
DBCC results for 'sys.sysprufiles'.
There are 3 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 14 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 130 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 54 rows in 1 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 488 rows in 9 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 0 rows in 0 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 167 rows in 2 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 318 rows in 3 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.sysaudacts'.
There are 0 rows in 0 pages for object "sys.sysaudacts".
DBCC results for 'sys.sysobjvalues'.
There are 168 rows in 33 pages for object "sys.sysobjvalues".
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 147 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 106 rows in 1 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.syscompfragments'.
There are 0 rows in 0 pages for object "sys.syscompfragments".
DBCC results for 'sys.sysftstops'.
There are 0 rows in 0 pages for object "sys.sysftstops".
DBCC results for 'sys.sysqnames'.
There are 97 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 99 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 18 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 0 rows in 0 pages for object "sys.syssoftobjrefs".
DBCC results for 'sys.filestream_tombstone_1522104463'.
There are 0 rows in 0 pages for object "sys.filestream_tombstone_1522104463".
DBCC results for 'sys.syscommittab'.
There are 0 rows in 0 pages for object "sys.syscommittab".
DBCC results for 'Data_Table1'.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:1524) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:1524). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:1525) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:1525). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:3125) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:3125). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:5820) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:5820). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:5821) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:5821). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:6077) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:6077). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:12285) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:12285). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:20317) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:20317). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:22044) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:22044). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:22045) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:22045). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:22940) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:22940). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:27677) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:27677). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:28253) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:28253). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:29276) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:29276). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:34389) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:34389). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:34390) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:34390). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:40088) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:40088). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:42513) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:42513). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:43509) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:43509). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:43700) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:43700). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:43765) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:43765). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:48229). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:48245) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:52989) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:52989). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
There are 2989145 rows in 49756 pages for object "Data_table1".
CHECKDB found 0 allocation errors and 46 consistency errors in table 'Data_table1' (object ID 1685581043).
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".
CHECKDB found 0 allocation errors and 46 consistency errors in database 'My_data'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (My_data).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
September 4, 2011 at 11:04 am
Got a clean backup? (a backup without the corruption)
If not, take the database into single user mode and run the following:
DBCC CheckDB('My_data', REPAIR_ALLOW_DATA_LOSS)
You will lose quite a lot of data (all the rows on about 22 pages) in the table 'Data_table1' if you do that.
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
September 4, 2011 at 11:08 am
While i run above mentioned command ,i have below mentioned error
Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
September 4, 2011 at 11:15 am
The SQL Service isn't running. Start it.
No backup? You are going to lose data by repairing.
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
September 4, 2011 at 12:52 pm
thanks,I have littile data losss which i can import from other sources.
September 4, 2011 at 1:02 pm
Great, now fix your backup strategy and make sure you're running regular integrity checks.
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
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply