Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Q&A with Qlik - Qlik Cloud Migration: Questions about migrating to Qlik Cloud? Catch the latest replay!
cancel
Showing results for 
Search instead for 
Did you mean: 
DendyLazuardi
Partner - Contributor II
Partner - Contributor II

MySQL [mysqld-5.1.31-community-log]Unknown character set: 'utf16'

Hello,

i have an error mysql to mysql and i'm using version 5.1. 
i'm running initial load and using cdc in my task, and here the error:

Handling new table 'master'.'replica__ct' failed
execute create table statement failed, statement CREATE TABLE `master`.`replica__ct` ( `header__change_seq` VARCHAR(35) NOT NULL, `header__change_oper` VARCHAR(1) NOT NULL, `header__change_mask` VARBINARY(128), `header__stream_position` VARCHAR(128) NOT NULL, `header__operation` VARCHAR(12) NOT NULL, `header__transaction_id` VARCHAR(32) NOT NULL, `header__timestamp` VARCHAR(37) NOT NULL, `no` INTEGER, `nama` VARCHAR(10) CHARACTER SET utf16 )
RetCode: SQL_ERROR SqlState: HY000 NativeError: 1115 Message: [MySQL][ODBC 5.2(w) Driver][mysqld-5.1.31-community-log]Unknown character set: 'utf16'
Failed (retcode -1) to execute statement: 'CREATE TABLE `master`.`replica__ct` ( `header__change_seq` VARCHAR(35) NOT NULL, `header__change_oper` VARCHAR(1) NOT NULL, `header__change_mask` VARBINARY(128), `header__stream_position` VARCHAR(128) NOT NULL, `header__operation` VARCHAR(12) NOT NULL, `header__transaction_id` VARCHAR(32) NOT NULL, `header__timestamp` VARCHAR(37) NOT NULL, `no` INTEGER, `nama` VARCHAR(10) CHARACTER SET utf16 )'

 

can anyone know whats wrong from this error?

 

Thanks you,

Dendy

Labels (1)
1 Solution

Accepted Solutions
john_wang
Support
Support

Hi @DendyLazuardi ,

 

You can check which character sets are supported in your env by query:

mysql> show character set;

 

check if UTF16 appears in your list or not. And you can also try to create such a table manually to see why it report error.

However it's not important because MySQL 5.1 is not in support range, Replicate support MySQL versions 5.5, 5.6,  5.7 and 8.0 (for both source and target endpoint).

 

For MySQL 5.1 the only option is do Full Load ONLY task (you cannot enable CDC). Connect to 5.1 by using ODBC DSN.

 

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!

View solution in original post

1 Reply
john_wang
Support
Support

Hi @DendyLazuardi ,

 

You can check which character sets are supported in your env by query:

mysql> show character set;

 

check if UTF16 appears in your list or not. And you can also try to create such a table manually to see why it report error.

However it's not important because MySQL 5.1 is not in support range, Replicate support MySQL versions 5.5, 5.6,  5.7 and 8.0 (for both source and target endpoint).

 

For MySQL 5.1 the only option is do Full Load ONLY task (you cannot enable CDC). Connect to 5.1 by using ODBC DSN.

 

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!