Record a problem bothering me for days. First paste error:
space name jxtms/CostManage, which is outside the tablespace bounds. B
yte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
When MySQL5.7 table space during migration, when import tablespace, the time is always fixed to a table, connection failure error.
I thought it was a problem after the connection timeout, timeout parameter adjustment, found that the problem still exists.
View the error log and found that the above error message.
This error message is very strange, out of table space limitations, let me check ibdata parameters. Ibdata profiles and related to innodb_data_file_path = ibdata1: 256M: autoextend, adjusting the parameter to a larger value.
Re-run, the error still exists.
Baidu for a long time, no one can give the correct solution. Bite the bullet and search from foreign websites, rub, had found.
MySQL5.7 said to be a bug, you need to close the persistent statistics parameters (innodb_stats_persistent = OFF), to resolve.
Feeling reconstruction bright ah.
After modification, the error is really solved.
I do not know the use of Chinese children have not encountered this problem or Baidu a little clumsy, and quickly recorded it, ha ha amount.
note:
Persistent statistics parameter when the database is shut down, the storage statistics table to the local, when you open the database, these statistics will retain the appearance before the closure. So when you need to generate SQL execution plan, now do not need to collect statistical information, it is where the.
This parameter has just started optimized database SQL parsing efficiency. After closing, the efficiency is not, as a patch, you can write a script manually, after starting the database, automatic statistics update.