• 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.

Problem with Migration Manager (Collations)

U

unixlibre

Guest
Dear all,

I've ran into problems while running the migration manager to migrate from FreeBSD4.9/Plesk7.5.2 to FreeBSD6.0/Plesk8.0. The migration manager complains with

ERROR 1267 (HY000) at line 1: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='

It seems that all databases were created with latin1.

The knowledge base says that one must try setting character_set_connection and collation_connection to utf8, which is not entirelly true because collation_connection sould be set to utf8_general_ci.

One way of setting this vars is with the init_connection parameter in my.cnf. The problem is that for admin users, this is not executed (for "security" reasons as stated in mysql docs), so putting this setting in my.cnf has no effect at all.

Anyone of you has a workaround for this?

Thank you in advance.
Antonio
 
Back
Top