Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 32.6Mb
PDF (A4) - 32.6Mb
PDF (RPM) - 30.6Mb
HTML Download (TGZ) - 7.8Mb
HTML Download (Zip) - 7.9Mb
HTML Download (RPM) - 6.7Mb
Man Pages (TGZ) - 143.2Kb
Man Pages (Zip) - 202.3Kb
Info (Gzip) - 3.0Mb
Info (Zip) - 3.0Mb


MySQL 8.0 Reference Manual  /  ...  /  ibd2sdi — InnoDB Tablespace SDI Extraction Utility

Pre-General Availability Draft: 2017-06-23

4.6.1 ibd2sdi — InnoDB Tablespace SDI Extraction Utility

ibd2sdi is a utility for extracting serialized dictionary information (SDI) from InnoDB tablespace files. SDI data is present in persistent InnoDB tablespace files as of MySQL 8.0.2.

ibd2sdi can be run on file-per-table tablespace files (*.ibd files), general tablespace files (*.ibd files), and system tablespace files (ibdata* files). ibd2sdi is not supported for use with the global data dictionary tablespace, the shared temporary tablespace, or undo log tablespaces.

ibd2sdi can be used at runtime or while the server is offline. During DDL operations, ROLLBACK, or undo log purge operations related to SDI records, there may be a short interval of time when ibd2sdi fails to read SDI data stored in the tablespace.

ibd2sdi performs an uncommitted read of SDI records from the specified tabelespace. Redo logs and undo logs are not accessed.

Invoke the ibd2sdi utility like this:

shell> ibd2sdi [options] file_name1 [file_name2 file_name3 ...]

ibd2sdi supports multi-file tablespaces like the InnoDB system tablespace, but it cannot be run on more than one tablespace at a time. For multi-file tablespaces, specify each file:

shell> ibd2sdi ibdata1 ibdata2

The files of a multi-file tablespace must be specified in order of the ascending page number. If two successive files have the same space ID, the later file must start with the last page number of the previous file + 1.

ibd2sdi outputs SDI records (containing id, type, and data fields) in JSON format.

ibd2sdi Options

ibd2sdi supports the following options:

  • --help, -h

    Displays command line help. Example usage:

    shell> ibd2sdi --help
  • --version, -v

    Displays MySQL version information. Example usage:

    shell> ibd2sdi --version
  • --dump-file=, -d

    Dumps serialized dictionary information (SDI) into the specified dump file. If a dump file is not specified, the tablespace SDI is dumped to stdout. Example usage:

    shell> ibd2sdi --dump-file=file_name ../data/test/t1.ibd
  • --read=#, -r #

    Reads from the specified copy of the serialized dictionary information (SDI). Permissible values are 0 or 1. Example usage:

    shell> ibd2sdi --read=1 ../data/test/t1.ibd
  • --skip-data, -s

    Skips retrieval of data field values from the serialized dictionary information (SDI) records and only retrieves the id and type field values, which are primary keys for SDI records. Example usage:

    shell> ibd2sdi --skip-data ../data/test/t1.ibd
  • --id=#, -i #

    Retrieves serialized dictionary information (SDI) records matching the specified id. All records are scanned.

    shell> ibd2sdi --id=701 ../data/test/t1.ibd
  • --type=#, -t #

    Retrieves serialized dictionary information (SDI) records matching the specified tablespace object type. All records are scanned.

    shell> ibd2sdi --type=3 ../data/test/t1.ibd
  • --strict-check, -c

    Specifies a strict checksum algorithm for validating the checksum of pages that are read. Options include innodb, crc32, and none.

    In this example, the strict version of the innodb checksum algorithm is specified:

    shell> ibd2sdi --strict-check=innodb ../data/test/t1.ibd

    In this example, the strict version of crc32 checksum algorithm is specified:

    shell> ibd2sdi -c crc32 ../data/test/t1.ibd

    If you do not specify the --strict-check option, validation is performed against non-strict innodb, crc32 and none checksums.

  • --no-check, -n

    Skips checksum validation for pages that are read. Example usage:

    shell> ibd2sdi --no-check ../data/test/t1.ibd

User Comments
Sign Up Login You must be logged in to post a comment.