myisam_ftdump — Display Full-Text Index information Running innochecksum on Multiple System Tablespace Files Note 4.6.3 myisam_ftdump — Display Full-Text Index information 560 The index on  id  is index 0 and the  FULLTEXT  index on  txt  is index 1. If your working directory is the test  database directory, invoke  myisam_ftdump  as follows: Example: Suppose that the  test  database contains a table named  mytexttable  that has the following definition: The  tbl_name  argument should be the name of a  MyISAM  table. You can also specify a table by naming its index file (the file with the  .MYI  suffix). If you do not invoke  myisam_ftdump  in the directory where the table files are located, the table or index file name must be preceded by the path name to the table’s database directory. Index numbers begin with 0. myisam_ftdump [ options ]  tbl_name index_num Invoke  myisam_ftdump  like this: myisam_ftdump  scans and dumps the entire index, which is not particularly fast. On the other hand, the distribution of words changes infrequently, so it need not be run often. myisam_ftdump  displays information about  FULLTEXT  indexes in  MyISAM  tables. It reads the MyISAM  index file directly, so it must be run on the server host where the table is located. Before using myisam_ftdump , be sure to issue a  FLUSH TABLES  statement first if the server is running. Running  innochecksum  on multiple files in the same tablespace is not supported on Windows operating systems, as Windows shells such as  cmd.exe  do not support glob pattern expansion. On Windows systems,  innochecksum  must be run separately for each system tablespace file. For example: Refer to the  innochecksum  options information for more information about the “-”  option. cat ibdata* | innochecksum - The three files ( ibdata1 ,  ibdata2 , and  ibdata3 ) form one logical system tablespace. To run innochecksum  on multiple files that form one logical system tablespace,  innochecksum  requires the  - option to read tablespace files in from standard input, which is equivalent to concatenating multiple files to create one single file. For the example provided above, the following  innochecksum  command would be used: ./bin/mysqld --no-defaults --innodb-data-file-path="ibdata1:10M;ibdata2:10M;ibdata3:10M:autoextend" By default, there is only one  InnoDB  system tablespace file ( ibdata1 ) but multiple files for the system tablespace can be defined using the  innodb_data_file_path  option. In the following example, three files for the system tablespace are defined using the  innodb_data_file_path  option:  ibdata1 , ibdata2 , and  ibdata3 . innochecksum.exe ibdata1 innochecksum.exe ibdata2 innochecksum.exe ibdata3 CREATE TABLE mytexttable ( id INT NOT NULL, txt TEXT NOT NULL, PRIMARY KEY (id), FULLTEXT (txt) ) ENGINE=MyISAM;