|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
|
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? Can you use a better subject line? "question" is pretty generic, and since
you already asked a "question", many people will think this is a follow-up to your previous question. > Server: Msg 8928, Level 16, State 1, Line 1 Hopefully you have a backup of the database where this table resides?> 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. You might try: DBCC CHECKDB('ibes','REPAIR_REBUILD ') And if that fails to clear up the DBCC errors, you can try: DBCC CHECKDB('ibes','REPAIR_ALLOW_DATA_LOSS') > DBCC results for 'sysindexes'. Wow, that is a lot of rows and a lot of pages!> There are 1953 rows in 127 pages for object 'sysindexes'. > how can I fix it without switching my database to single mode? As the statement says, I don't think you can issue that particular statement without being in single user mode. Are you more interested in repairing the database, or keeping a corrupt database up 24x7? You're going to have to choose. A Why can't I just repair one table instead of whole database?
Show quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:Opts09UiFHA.3448@TK2MSFTNGP12.phx.gbl... > Can you use a better subject line? "question" is pretty generic, and since > you already asked a "question", many people will think this is a follow-up > to your previous question. > > > 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. > > Hopefully you have a backup of the database where this table resides? > > You might try: > > DBCC CHECKDB('ibes','REPAIR_REBUILD ') > > And if that fails to clear up the DBCC errors, you can try: > > DBCC CHECKDB('ibes','REPAIR_ALLOW_DATA_LOSS') > > > DBCC results for 'sysindexes'. > > There are 1953 rows in 127 pages for object 'sysindexes'. > > Wow, that is a lot of rows and a lot of pages! > > > how can I fix it without switching my database to single mode? > > As the statement says, I don't think you can issue that particular statement > without being in single user mode. Are you more interested in repairing the > database, or keeping a corrupt database up 24x7? You're going to have to > choose. > > A > > > Why can't I just repair one table instead of whole database? (a) what is the harm?(b) in case there are other problems lurking in other tables. Anyway, you didn't seem willing to take the database offline... Okay Aaron,
thanks for your help, but after running BCC CHECKDB('ibes','REPAIR_ALLOW_DATA_LOSS') I still got same error, now what should I do? Server: Msg 8929, Level 16, State 1, Line 1 Object ID 2: Errors found in text ID 30122835968 owned by data record identified by RID = (1:214376:7) id = 1767677345 and indid = 8. Server: Msg 8929, Level 16, State 1, Line 1 Object ID 2: Errors found in text ID 30122901504 owned by data record identified by RID = (1:214376:8) id = 1767677345 and indid = 9. 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. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:869938), slot 0, text ID 30122835968 is referenced by page (1:1276089), slot 1, but was not seen in the scan. Server: Msg 8965, Level 16, State 1, Line 1 Table error: Object ID 2. The text, ntext, or image node at page (1:869938), slot 1, text ID 30122901504 is referenced by page (1:1276089), slot 3, but was not seen in the scan. DBCC results for 'ibes'. DBCC results for 'sysobjects'. There are 563 rows in 12 pages for object 'sysobjects'. DBCC results for 'sysindexes'. The repair level on the DBCC statement caused this repair to be bypassed. The system cannot self repair this error. The repair level on the DBCC statement caused this repair to be bypassed. The repair level on the DBCC statement caused this repair to be bypassed. The repair level on the DBCC statement caused this repair to be bypassed. The repair level on the DBCC statement caused this repair to be bypassed. There are 1953 rows in 127 pages for object 'sysindexes'. CHECKDB found 0 allocation errors and 6 consistency errors in table 'sysindexes' (object ID 2). Show quote "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message news:%23NONcdViFHA.2152@TK2MSFTNGP14.phx.gbl... > > Why can't I just repair one table instead of whole database? > > (a) what is the harm? > > (b) in case there are other problems lurking in other tables. > > Anyway, you didn't seem willing to take the database offline... > > The closest solution I get is this link,
http://support.microsoft.com/kb/890755 but I need to call for Microsoft support, since this hotfix is specific for this problem, they didn't post hotfix on their web site. I guess I need to drop it and recreate it then copy data from data center. hmm.... Show quote "Britney" <britneychen_2***@yahoo.com> wrote in message news:ePA0WvgiFHA.3608@TK2MSFTNGP12.phx.gbl... > Okay Aaron, > thanks for your help, but after running > > BCC CHECKDB('ibes','REPAIR_ALLOW_DATA_LOSS') > > I still got same error, now what should I do? > > > Server: Msg 8929, Level 16, State 1, Line 1 > Object ID 2: Errors found in text ID 30122835968 owned by data record > identified by RID = (1:214376:7) id = 1767677345 and indid = 8. > Server: Msg 8929, Level 16, State 1, Line 1 > Object ID 2: Errors found in text ID 30122901504 owned by data record > identified by RID = (1:214376:8) id = 1767677345 and indid = 9. > 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. > Server: Msg 8965, Level 16, State 1, Line 1 > Table error: Object ID 2. The text, ntext, or image node at page (1:869938), > slot 0, text ID 30122835968 is referenced by page (1:1276089), slot 1, but > was not seen in the scan. > Server: Msg 8965, Level 16, State 1, Line 1 > Table error: Object ID 2. The text, ntext, or image node at page (1:869938), > slot 1, text ID 30122901504 is referenced by page (1:1276089), slot 3, but > was not seen in the scan. > DBCC results for 'ibes'. > DBCC results for 'sysobjects'. > There are 563 rows in 12 pages for object 'sysobjects'. > DBCC results for 'sysindexes'. > The repair level on the DBCC statement caused this repair to be > bypassed. > The system cannot self repair this error. > The repair level on the DBCC statement caused this repair to be > bypassed. > The repair level on the DBCC statement caused this repair to be > bypassed. > The repair level on the DBCC statement caused this repair to be > bypassed. > The repair level on the DBCC statement caused this repair to be > bypassed. > There are 1953 rows in 127 pages for object 'sysindexes'. > CHECKDB found 0 allocation errors and 6 consistency errors in table > 'sysindexes' (object ID 2). > > > "Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message > news:%23NONcdViFHA.2152@TK2MSFTNGP14.phx.gbl... > > > Why can't I just repair one table instead of whole database? > > > > (a) what is the harm? > > > > (b) in case there are other problems lurking in other tables. > > > > Anyway, you didn't seem willing to take the database offline... > > > > > >  
Other interesting topics
|
|||||||||||||||||||||||
