May 5, 2016 at 9:34 pm
I have 4 replicated publisher databases on server A that seems to be corrupted, and unfortunately the back that we have is way too old to restore . Now, my only option left as per dbcc checkdb is to use repair_allow_data_loss. Now, my question is when you run repair on the corrupted replication publication database does it impact replication by any means after the repair is completed, and can I first of all do a repair_allow_data_loss on replicated database. I mean if it is in replication, and published I can't take it in single_user mode...right?. If that is not an option, how would I repair the database...do I need to drop replication, and recreate it back etc.
Please let me know about the steps needed to be taken. I hope I am clear, and concise on this one.
E.g errors.
Attempt to fetch logical page (1:5440) in database 32 failed. It belongs to allocation unit 72057594044219392 not to 72057594043367424.
Attempt to fetch logical page (1:105616) in database 11 failed. It belongs to allocation unit 72057609049276416 not to 72057609084469248.
Attempt to fetch logical page (1:64808) in database 13 failed. It belongs to allocation unit 72057609071820800 not to 72057609051897856.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply