• 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 ERROR 1273 (HY000) utf8mb4_unicode_520_ci

E

eslammahmoud

New Pleskian
Failed to copy content of database 'move3afs_wp'
Migration tools tried to perform operation in 1 attempts: Restoration of MySQL database failed. Most probable reason:

Target MySQL server does not contain necessary character set.
Most likely it is required to have at least MySQL 5.5 to restore such database.

Proposed solutions:
*) Obtain another target server which has OS providing appropriate MySQL server version.
For example, CentOS 6 provides MySQL 5.1 by default, while CentOS 7 provides MySQL 5.5 by default.
*) Connect another external MySQL server to the target server with appropriate MySQL version.
Configure that server as default, or specify it in service plan to which subscriptions are assigned to.
Remove migrated subscription from the target server and start migration once more.
*) Upgrade MySQL server on the target server to appropriate version, then run migration once more (no need to
remove subscriptions from target - just run migration over existing domains). For example, for CentOS you could use
packages provided by EPEL repositories. This way is not recommended for servers already running in production.

Here is the original error message reported by MySQL client when restoring the database:
ERROR 1273 (HY000) at line 25: Unknown collation: 'utf8mb4_unicode_520_ci'

How to solve the problem?
 
You must log in or register to reply here.

Similar threads

LorisMod
Question Migration from plesk to plesk db error
Replies
12
Views
4K
LorisMod
LorisMod
K
Resolved Migrator - Unable to connect to the destination PostgreSQL database server.
Replies
4
Views
1K
BigBlock
B
S
Issue Error: Connection to the database server failed: SQLSTATE[HY000]: General error: 1273 Unknown collation: 'UTF8_GENERAL_CI'
Replies
5
Views
4K
Peter Debik
P
Daerik
Resolved Plesk Migrator Failing to Sync Database Records After Server Upgrade
Replies
8
Views
1K
Maarten
M
R
Question Switching to new server
Replies
15
Views
3K
AYamshanov
AYamshanov
Back
Top