DWH setup version 13.19 in cluster mode bailing out


#1

Hello,

I’m installing version 13.19 in cluster mode and I’m getting this error during the setup of DWH:

installation_log.log

now executing /opt/kaltura/dwh/ddl//dw//ip_ranges.sql
now executing /opt/kaltura/dwh/ddl//dw//locations.sql
now executing /opt/kaltura/dwh/ddl//dw//locations_init.sql
now executing /opt/kaltura/dwh/ddl//dw//ip_ranges_init.sql
now executing /opt/kaltura/dwh/ddl//dw//update_location_details.sql
ERROR 1267 (HY000) at line 36: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation ‘=’
1
Error - bailing out!

I think this is related to the call to the stored procedure update_location_details

Any ideas why?

Thanks


#2

Hi @amanadas,

What MySQL version are you using?


#3

Hi jess,

It’s 5.6.25.


#4

Hi @amanadas,

Won’t work, I’m afraid. Please use MySQL 5.5. I recommend the Percona packages.


#5

Thank you Jess, I am going to down grade the MySQL installation.

Regards,


#6

Hello,

The MySQL was re-installed and is now version 5.5.44, but I’m getting the same error.


now executing /opt/kaltura/dwh/ddl//dw//ip_ranges_init.sql
now executing /opt/kaltura/dwh/ddl//dw//update_location_details.sql
ERROR 1267 (HY000) at line 36: Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation ‘=’
1
Error - bailing out!

The re-install/reconfiguration of Kaltura was done like this:

  • The MySQL server was clean and no kaltura databases present;
  • In the Front end I called /opt/kaltura/bin/kaltura-db-config.sh “HOST” “ADMIN” “PASS” “PORT”;
  • In the Back end I called /opt/kaltura/bin/kaltura-dwh-config.sh ~/config.ans

The Cluster has this configured roles:

FRONT END

  • SPHINX
  • FRONT END

VOD

  • NGINX
  • SPHINX

BACK END

  • BATCH
  • DWH

Any ideas?

Thanks


#7

Hi @amanadas,

Can you try adding these directives under the [mysqld] section in your my.cnf?

character-set-server=utf8
collation-server=utf8_general_ci

You will need to reload your MySQL daemon after doing so.
Note that you do not have to reinstall/reconfigure the entire instance from scratch in order to repopulate the DWH databases.
You can run:

# /opt/kaltura/bin/kaltura-drop-dwh.sh

which will drop all DWH DBs [note that this cannot be reversed and all data will be lost] and then:

# /opt/kaltura/bin/kaltura-dwh-config.sh /path/to/config.ans

#8

Hello @jess,

After changing collation_connection->utf8_general_ci, collation_database->utf8_general_ci and collation_server->utf8_general_ci and recreating the database so that it reflects these changes in all databases and tables, the installation of the DWH run until the end.

Thanks for all the help.


#9

Welcome @amanadas. Glad to hear we’re good.