Rechercher dans le manuel MySQL

15.20.3 Troubleshooting InnoDB Data Dictionary Operations

Table des matières

Information about table definitions is stored in the InnoDB data dictionary. If you move data files around, dictionary data can become inconsistent.

If a data dictionary corruption or consistency issue prevents you from starting InnoDB, see Section 15.20.2, “Forcing InnoDB Recovery” for information about manual recovery.

Cannot Open Datafile

With innodb_file_per_table enabled (the default), the following messages may appear at startup if a file-per-table tablespace file (.ibd file) is missing: 

[ERROR] InnoDB: Operating system error number 2 in a file operation.
[ERROR] InnoDB: The error means the system cannot find the path specified.
[ERROR] InnoDB: Cannot open datafile for read-only: './test/t1.ibd' OS error: 71
[Warning] InnoDB: Ignoring tablespace `test/t1` because it could not be opened.

To address the these messages, issue DROP TABLE statement to remove data about the missing table from the data dictionary.

 

Restoring Orphan File-Per-Table ibd Files

This procedure describes how to restore orphan file-per-table .ibd files to another MySQL instance. You might use this procedure if the system tablespace is lost or unrecoverable and you want to restore .idb file backups on a new MySQL instance.

The procedure is not supported for general tablespace .ibd files.

The procedure assumes that you only have .ibd file backups, you are recovering to the same version of MySQL that initially created the orphan .idb files, and that .idb file backups are clean. See Section 15.6.1.2, “Moving or Copying InnoDB Tables” for information about creating clean backups.

Tablespace copying limitations outlined in Section 15.6.3.7, “Copying Tablespaces to Another Instance” are applicable to this procedure.

  1. On the new MySQL instance, recreate the table in a database of the same name.

    1. mysql> CREATE DATABASE sakila;
    2.  
    3. mysql> USE sakila;
    4.  
    5. mysql> CREATE TABLE actor (
    6.          actor_id SMALLINT UNSIGNED NOT NULL AUTO_INCREMENT,
    7.          first_name VARCHAR(45) NOT NULL,
    8.          last_name VARCHAR(45) NOT NULL,
    9.          last_update TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    10.          PRIMARY KEY  (actor_id),
    11.          KEY idx_actor_last_name (last_name)
    12.        )ENGINE=InnoDB DEFAULT CHARSET=utf8;

  2. Discard the tablespace of the newly created table.

    1. mysql> ALTER TABLE sakila.actor DISCARD TABLESPACE;

  3. Copy the orphan .idb file from your backup directory to the new database directory. 

    shell> cp /backup_directory/actor.ibd path/to/mysql-5.7/data/sakila/

  4. Ensure that the .ibd file has the necessary file permissions.

  5. Import the orphan .ibd file. A warning is issued indicating that InnoDB will attempt to import the file without schema verification.

    1. mysql> ALTER TABLE sakila.actor IMPORT TABLESPACE; SHOW WARNINGS;    
    2. Query OK, 0 rows affected, 1 warning (0.15 sec)
    3.  
    4. Warning | 1810 | InnoDB: IO Read error: (2, No such file or directory)
    5. Error opening './sakila/actor.cfg', will attempt to import
    6. without schema verification

  6. Query the table to verify that the .ibd file was successfully restored.

    1. mysql> SELECT COUNT(*) FROM sakila.actor;
    2. +----------+
    3. | count(*) |
    4. +----------+
    5. |      200 |
    6. +----------+

Rechercher dans le manuel MySQL

Traduction non disponible

Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.

Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-innodb-troubleshooting-datadict.html

L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.

Références

  1. Consulter le document html Langue du document :en Manuel MySQL : https://dev.mysql.com/

Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.

Table des matières Haut