|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
fixing an errorDBCC CHECKTABLE (sysindexes, 255) Result: Server: Msg 8928, Level 16, State 1, Line 1 Object ID 2, index ID 255: Page (1:869938) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 2, index ID 255, page (1:869938). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1. DBCC results for 'sysindexes'. There are 1953 rows in 127 pages for object 'sysindexes'. CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2). repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (ibes.dbo.sysindexes, (255)Text ). I tried to fix it, when I run the following query, DBCC CHECKTABLE (sysindexes, repair_allow_data_loss) Result: Server: Msg 7919, Level 16, State 3, Line 1 Repair statement not processed. Database needs to be in single user mode. DBCC execution completed. If DBCC printed error messages, contact your system administrator. What could be the problem? how can I fix it without switching my database to single mode? Maybe there is a way? Can I drop the index 255 and recreate it? Hi
You may want to try exporting all the data, truncating the table and re-importing the data, but if you have any foreign keys it could start to get messy! John Show quote "Britney" wrote: > Hi guys, > > DBCC CHECKTABLE (sysindexes, 255) > > Result: > > Server: Msg 8928, Level 16, State 1, Line 1 > Object ID 2, index ID 255: Page (1:869938) could not be processed. See other > errors for details. > Server: Msg 8939, Level 16, State 1, Line 1 > Table error: Object ID 2, index ID 255, page (1:869938). Test (IS_ON > (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1. > DBCC results for 'sysindexes'. > There are 1953 rows in 127 pages for object 'sysindexes'. > CHECKTABLE found 0 allocation errors and 2 consistency errors in table > 'sysindexes' (object ID 2). > repair_allow_data_loss is the minimum repair level for the errors found by > DBCC CHECKTABLE (ibes.dbo.sysindexes, (255)Text ). > > > > > > I tried to fix it, when I run the following query, > > DBCC CHECKTABLE (sysindexes, repair_allow_data_loss) > > Result: > Server: Msg 7919, Level 16, State 3, Line 1 > Repair statement not processed. Database needs to be in single user mode. > DBCC execution completed. If DBCC printed error messages, contact your > system administrator. > > > What could be the problem? > how can I fix it without switching my database to single mode? > Maybe there is a way? Can I drop the index 255 and recreate it? > > > > |
|||||||||||||||||||||||