Following a server crash, the automatic recovery of InnoDB fails. How would you begin to
manually repair the InnoDB tables?
A.
Start the server with the – innodb_recover_options option set to FORCE.
B.
Start the server with the – innodb_force_recovery option set to a non-zero value.
C.
Start the server as usual, and then execute the REPAIR TABLE command.
D.
Start the server as usual, and then execute the CHECK TABLE command.
B
To investigate database page corruption, you might dump your tables from the database with SELECT … INTO OUTFILE. Usually, most of the data obtained in this way is intact. Serious corruption might cause SELECT * FROM tbl_name statements or InnoDB background operations to crash or assert, or even cause InnoDB roll-forward recovery to crash. In such cases, you can use the innodb_force_recovery option to force the InnoDB storage engine to start up while preventing background operations from running, so that you can dump your tables.
B