Your choices are restoring from a backup or trying to identify and unpick the damage.
On the first one, you've ruled out XML, so the question should be down to getting the latest database backup and restoring that.
The second option is risky and gets exponentially more time consuming for each error. I'd look at the logs to see if there are hints of how bad it is in there to start with, but you could be looking at months of unpicking damage. Reverting to a backup is almost certainly the right approach.
It depends on the nature of the damage - if you can unpick the damage, then you don't need to revert to a backup. But as I already said, it's potentially an immensely difficult task.
When you say "corrupted", the question really is "how badly corrupted is it". And, in fact, "how do you know it's corrupt"
The stupid thing I did with the MySQL can be found here:-
While I am trying the options from Confluence end, I am also trying to recover my DB.
Oh, right. It's not really "corrupt" then, it's "completely destroyed"
You need the backups. I'm afraid if you haven't got any, then you've wiped your installation and lost everything.
A MySQL expert may be able to help you here - I have a feeling that if you created a new, clean installation of MySQL and then installed a new, clean version of Confluence using it so you get all the tables and files populated, and then moved your old stuff back into it, you might be able to rescue something. But I'm really not a MySQL expert and I am guessing, so I really wouldn't bet on it.
Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time! We're looking for people to participate in a remote 1-hr workshop...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs