Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
cdc
Partner - Contributor III
Partner - Contributor III

Failed Test Connection for MySQL v8.0 as Source Endpoint

Hi all,

Recently my client upgraded their MySQL to version 8.0 on Qlik Replicate version 6.6.0.546. Unfortunately, it failed when trying to test the connection. Any idea or solution regarding this case? in addition, this happen in production environment. Thank you

Akbar

5 Replies
john_wang
Support
Support

Hello @cdc ,

Thanks for reaching out to Qlik Community!

The problem is Qlik Replicate v6.6 does not support characterset UTF8MB4. This charset is supported from version v7.0.

However versions v6.6 and 7.0 and other old versions had reached end of support (EOS) date. Please upgrade to supported major versions, version 2023.11 is highly recommended.

Hope this helps.

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
cdc
Partner - Contributor III
Partner - Contributor III
Author

Hi John,

 

Thank you for the response, is there any solution beside upgrade the Qlik version?

 

Thank you

john_wang
Support
Support

Hello @cdc ,

Thanks for the feedback.

UTF8MB4 is the default charset in MySQL 8.0 and up, while in MySQL 5.7 and lower versions it's  UTF8MB3. Maybe you can specify UTF8MB3 in MySQL server configuration file (need restart MySQL Service) and try again. However as Replicate 6.6 is out of support, it's risk to run it in a PROD system.

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
cdc
Partner - Contributor III
Partner - Contributor III
Author

Hi John,

Is there any best practice to configure from Qlik for this case?

Thanks

john_wang
Support
Support

Hello @cdc ,

It's pure MySQL server settings, It's better to work with your DBA to setup the MySQL.

Thanks,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!