Documentation Home
MySQL 8.0 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 33.0Mb
PDF (A4) - 33.0Mb
PDF (RPM) - 31.0Mb
HTML Download (TGZ) - 7.9Mb
HTML Download (Zip) - 7.9Mb
HTML Download (RPM) - 6.7Mb
Man Pages (TGZ) - 143.7Kb
Man Pages (Zip) - 203.9Kb
Info (Gzip) - 3.0Mb
Info (Zip) - 3.0Mb

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

Pre-General Availability Draft: 2017-08-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.3.

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

ibd2sdi can be used at runtime or while the server is offline. During DDL operations, ROLLBACK operations, and undo log purge operations related to SDI, 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 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 (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
  • --debug[=debug_options], -# [debug_options]

    Prints a debug log. For debug options, refer to Section 28.5.3, “The DBUG Package”. Example usage:

    shell> ibd2sdi --debug=d:t /tmp/ibd2sdi.trace
  • --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
  • --skip-data, -s

    Skips retrieval of data field values from the serialized dictionary information (SDI) 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) matching the specified schema, table, or tablespace object id. An object id is unique to the object type. Schema, table, and tablespace object id's are also found in the id column of the mysql.schemata, mysql.tables, and mysql.tablespace data dictionary tables. For information about data dictionary tables, see Section 14.1, “Data Dictionary Schema”.

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

    Retrieves serialized dictionary information (SDI) matching the specified object type. SDI is provided for schema (type=0), table (type=1), and tablespace (type=2) objects.

    shell> ibd2sdi --type=2 ../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.