Post reply

Corrupted cluster index on a replicated table.

  • January 29, 2004 at 11:54 am

    #101863

    Corrupted cluster index on a replicated table.

    I can fix the problem - I/O error (bad page ID) detected during read at offset. DBCC checkdb shows a corruption on an index. Normally I would drop/recreate the index or run checkdb with a repair_rebuild, but this table is replicated.

    What steps are needed to fix the problem when the table is replicated?

    I'm using transaction replication and several of the subscribers run fulltext index, dropping the publication is not a pleasant thought, considering the time it will take to republish, replicate and recreate the indexes.

    Can just one article be taken out, fixed, and then republished? I find nothing to support this in BOL

    SQL 2K


    John Zacharkan

  • January 29, 2004 at 6:11 pm

    #492274

    This forum requires some serious enhancements! I have to rewrite the entire post because the "Edit" button has cleared out the original post!

    You should place the Database in singleuser mode(this will prevent any further transactions) so that you get the connection. Then drop and recreate your index!

    Oh! Don't forget to disable "Single User Mode"

    Kindest Regards,

Viewing 2 posts - 1 through 1 (of 1 total)

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