Symptoms
-
The following error appears during a migration pre-check on the target server:
In InnoDB 5.6 (both in MySQL 5.6 and MariaDB 10.0/10.1) server has variable innodb_strict_mode=0 by default.
So you can create table with wrong ROW_FORMAT option and warning will be reported.
In InnoDB 5.7 (both in MySQL 5.7 and MariaDB 10.2) server has variable innodb_strict_mode=1 by default.
Migration from source, hosted with previous version of InnoDB will not be possible to target
with current version of InnoDB and error will be issued if innodb_strict_mode is set to default.
Set variable innodb_strict_mode to OFF on target to avoid the migration errors.
Here is the link describing the problem
https://jira.mariadb.org/browse/MDEV-11305Here is a list of affected subscriptions:
- example.com
Cause
Strict mode is enabled on the newer versions of MySQL/MariaDB by default.
Resolution
Note: Once the migration will finish, it is safe to enable back the innodb_strict_mode option in Plesk Obsidian.
For Linux
-
Connect to the target server via SSH.
-
Add innodb_strict_mode to MySQL configuration:
2.1. Open MySQL configuration file/etc/my.cnfin a text editor, for example, in the vi editor:vi /etc/my.cnf
Note: For Debian/Ubuntu the path is /etc/mysql/my.cnf
2.2. Add innodb_strict_mode=OFF under the [mysqld] section:
[mysqld]
innodb_strict_mode=OFF
2.3. Save the changes and close the file.
- Restart MySQL service:
# service mysql restart || service mariadb restart || service mysqld restart
- Proceed with the migration.
For Windows
- Connect to the target server via RDP.
- Open MySQL configuration file
%plesk_dir%DatabasesMySQLmy.iniin a text editor.
2.1 Addinnodb_strict_mode=OFFunder the [mysqld] section:[mysqld]
innodb_strict_mode=OFF2.3. Save the changes and close the file
-
Restart MySQL service via Plesk Services Monitor (it can be found in the system tray).
-
Proceed with the migration