Monday, May 3, 2010

Resolving MySQL Error- “Page Directory corruption: supremum not pointed to”

MySQL is a widely used RDBMS (Relations Database Management System), which uses two different storage engines- InnoDB and MyISAM. InnoDB is included as a standard storage engine in all modern binaries, which are distributed by MySQL AB. It has ACID (Atomicity, Consistency, Isolation, Durability) compliant-transaction support, along with the foreign key support. However in some situations, you may encounter errors while starting the InnoDB database that indicate database corruption. Corruption renders your database tables inaccessible and cause serious data loss situations. In order to retrieve the damaged database tables you need to restore them from an updated backup. But, if the backup is unavailable, go for MySQL Repair solutions.

In a practical scenario, you may encounter startup failure of the InnoDB storage engine with “Signal 11”, prefaced by an unexpected shutdown of the InnoDB. At the same time, you may also come across the below error message:

“Page directory corruption: supremum not pointed to.”

The server startup variants can not complete successfully. After startup failure, you see the log entries in .err file of MySQL application, similar to the following one:

“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

This issue is caused by the corruption of page directory of InnoDB storage engine. The same problem may also occur if the storage engine or database are corrupted.

This overall behavior of MySQL application indicates database corruption and needs MySQL Repair.

Resolution

You can sort out this problem by replacing the MySQL Server dir with the most recent backup. In case the backup is not updated or is not available in place, situations can be quite difficult to handle manually.

In such circumstances, one has to Repair MySQL Database using third party applications. They are particularly designed to methodically scan the database tables and repair, and restore them. You can Recover MySQL database on your own using these self-descriptive applications having interactive user interface.

MySQL is an advanced software that successfully restores damaged database in all corruption scenarios. It works well with MySQL 5.x and 4.x. The software supports both InnoDB and MyISAM storage engines and restores all database objects.

No comments:

Post a Comment