Mysql, a popular RDBMS (Relational Database management System) makes use of two storage engines i.e. InnoDB and MyISAM in which InnoDB is considered as a standard storage engine that ACID (Atomicity, Consistency, Isolation, Durability) properties along with foreign key support. But at times, you can face problems when trying to start Innodb database which can further lead to errors like Page directory corruption and inaccessibility even data loss situations. In such situations, use an updated backup or go for mysql repair tool.

Consider a practical scenario where you are trying to start Innodb database engine with Signal 11 after abnormal system shutdown, but you fail to do so and get the following error on screen:

"Page directory corruption: supremum not pointed to."

After getting the error message, the following log entries are registered in the log files:

"InnoDB: Error: all log files must be created at the same time. InnoDB: All log files must be created also in database creation. InnoDB: If you want bigger or smaller log files, shut down the InnoDB: database and make sure there were no errors in shutdown. InnoDB: Then delete the existing log files. Edit the .cnf file InnoDB: and start the database again. 060218 16:45:01 [ERROR] Default storage engine (InnoDB) is not available 060218 16:45:01 [ERROR] Aborting"

Cause:

The foremost reason for the occurrence of page directory corruption supremum not pointed to error is the corruption of Innodb engine’s page directory. The same behavior is encountered at the time of database corruption.

Solution:

In order to fix page directory corruption mysql error, you need to replace the mysql server directory with the help of latest backup. But in the absence of an updated backup, manual resolution to fix innodb page directory corruption error can be quite difficult. So, the best would be to use mysql repair tool that performs the task of mysql repair innodb database engine completely and efficiently without much involvement of users.