• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Mysql tables innodb lost after alter table

Nicola

Basic Pleskian
Hi,
I have a problem for a couple of days with mysql (5.7) and innodb tables, I try to explain:

I have a main database (dbDeveloping) and a series of databases in production (db1Production, db2Production, ...), when I modify the structure of some tables in "db1Developing", through a php script I update the structure of the tables in "db1Production", "db2Production", ... .

In a table I added two columns of type "date" and during the updating phase in some databases it happens that the table disappears and I can not recreate it anymore.

I checked in /var/lib/mysql/db1Production/ and there are table.frm and table.ibd files but I can no longer access the tables via mysql.

At the moment when this problem occurs mysql no longer responds and I am forced to restart it.

I attach some mysql logs



This morning I have lots of lines with this warning

Code:
2019-02-20T07:38:08.940353Z 648090 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2019-02-20T07:38:08.940366Z 648090 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade

Thanks in advance for the help
 

Attachments

  • mysqld-log.pdf
    24.3 KB · Views: 1
  • my-cnf.pdf
    20.6 KB · Views: 1
I'd do backup and then run mysql_upgrade just as warnings suggest. Similar issue: MySQL :: InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name
If that wouldn't solve the problem then MySQL :: MySQL 5.7 Reference Manual :: 14.21.3 Troubleshooting InnoDB Data Dictionary Operations should be of some help.

Also as of mySQL 5.7 ERROR_FOR_DIVISION_BY_ZERO is deprecated and one should use STRICT_TRANS_TABLES or TRADITIONAL sql mode along with it: MySQL :: MySQL 5.7 Reference Manual :: 5.1.10 Server SQL Modes
 
Back
Top