Migration problems with mysql: Operation not allowed when innodb_forced_recovery > 0 [closed]

Commenting out the line

innodb_force_recovery = 1

in /etc/my.cnf thus:

# innodb_force_recovery = 1

made the mysql innodb tables in the database accessible. Apparently this setting causes innodb to become read-only. I hope this helps someone in the future. If you don’t have access to /etc/my.cnf on shared hosting, ask your host to fix it for you. When it’s commented out or non-existent in /etc/my.cnf, the it reverts to a default setting of 0.

For future reference, I hope this will help someone else who is using wordpress plugins that require innodb flavored tables. I know there was some concern that this may not have been the appropriate place for this question, but I suspect as more plugins and perhaps even WP starts using InnoDB, others may be glad for the crossover knowledge posted here.