sysindexes consistancy error

  • Help needed to rectify the error below on SQL 2K SP4, any suggestion is welcome (DBCC REPAIR ALLOW DATA LOSS couldn't fix it, all the backup contain this error). The backup can be restore into SQL 2K but not on SQL 2008. Thanks in advance for all the suggestion and help.

    DBCC CHECKDB WITH NO_INFOMSGS

    return the following error

    Server: Msg 8929, Level 16, State 1, Line 1

    Object ID 2: Errors found in text ID 1136355901440 owned by data record identified by RID = (1:118525:4) id = 1729349871 and indid = 10.

    Server: Msg 8929, Level 16, State 1, Line 1

    Object ID 2: Errors found in text ID 1136355966976 owned by data record identified by RID = (1:118525:5) id = 1729349871 and indid = 11.

    Server: Msg 8929, Level 16, State 1, Line 1

    Object ID 2: Errors found in text ID 1136356032512 owned by data record identified by RID = (1:118525:6) id = 1729349871 and indid = 12.

    Server: Msg 8965, Level 16, State 1, Line 1

    Table error: Object ID 2. The text, ntext, or image node at page (1:2580035), slot 2, text ID 1136355901440 is referenced by page (1:118525), slot 4, 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:2580035), slot 4, text ID 1136355966976 is referenced by page (1:118525), slot 5, 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:2580035), slot 9, text ID 1136356032512 is referenced by page (1:118525), slot 6, but was not seen in the scan.

    Server: Msg 8964, Level 16, State 1, Line 1

    Table error: Object ID 2. The text, ntext, or image node at page (1:3477818), slot 0, text ID 1136355901440 is not referenced.

    CHECKDB found 0 allocation errors and 7 consistency errors in table 'sysindexes' (object ID 2).

    CHECKDB found 0 allocation errors and 7 consistency errors in database 'SUN522AU'.

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply