topic Re: Does log-bin={Path to the binary log file] is correct parameter of MySQL8 ? in Qlik Replicate

Does log-bin={Path to the binary log file] is correct parameter of MySQL8 ?

khchoy — Wed, 15 Jul 2020 06:47:14 GMT

Hi All,

I test with MySQL 8 for source endpoint but it is not working with error.

00008396: 2020-07-15T15:34:34:247384 [SOURCE_CAPTURE ]E: Error 2019 (Can't initialize character set unknown (path: compiled_in)) connecting to MySQL server '192.168.3.106' [1020414] (mysql_endpoint_capture.c:275)
00008396: 2020-07-15T15:34:34:247414 [SOURCE_CAPTURE ]E: Errors in MySQL server binary logging configuration [1020414] (mysql_endpoint_imp.c:672)

I set my.cnf of source mysql 8

#for Qlik Replication
server_id=1
log-bin=/var/lib/mysql/binlog
binlog_format=row
expire_logs_days=5
binlog_row_image=full
binlog_checksum=CRC32
log_slave_updates=1

but I cantnot found 'log-bin' in mysql 8.

in the QR User guide said

log-bin=<path> Path to the binary log file (without an extension).
Example:
log-bin=E:\MySql_Logs\BinLog

I use linux server for Mysql 8 and correct binlog path is /var/lib/mysql/

What's wrong ?

Regards,

Re: Does log-bin={Path to the binary log file] is correct parameter of MySQL8 ?

john_wang — Wed, 15 Jul 2020 07:07:10 GMT

Hi KwangHo,

The default char set of MySQL changed from UTF8 to UTF8MB4 from version 8.0.

The current Replicate versions does not support MySQL v8.x with char set UTF8MB4 yet. If you change the MySQL char set to UTF8 then it's fine. For example in file "my.ini" section "[mysqld]" add:

======================================

init-connect='SET NAMES utf8'
character-set-server=utf8

======================================

The plan is that we will support UTF8MB4 in Nov 2020 version.

Regards,

John.

Re: Does log-bin={Path to the binary log file] is correct parameter of MySQL8 ?

khchoy — Wed, 15 Jul 2020 07:39:22 GMT

Why it does not explained v6.6 User Guide ?

after update my.cnf

error is changed

00008897: 2020-07-15T16:25:00:632450 [SOURCE_CAPTURE ]V: Connecting MariaDB to 192.168.3.106 (mysql_endpoint_capture.c:200) ==> why QR recognized MariaDB ?
00008897: 2020-07-15T16:25:00:657035 [SOURCE_CAPTURE ]T: Error 2058 (Plugin caching_sha2_password could not be loaded: /usr/local/lib/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory) connecting to MySQL server '192.168.3.106' [1020414] (mysql_endpoint_capture.c:275)

==> Does Error 2058 from QR or ODBC ?
00008897: 2020-07-15T16:25:00:657067 [SOURCE_CAPTURE ]T: Errors in MySQL server binary logging configuration [1020414] (mysql_endpoint_imp.c:672)
00008897: 2020-07-15T16:25:00:657134 [SOURCE_CAPTURE ]T: Stream component 'st_0_ovm106-MySQL8-S' terminated [1020414] (subtask.c:1537)
00008897: 2020-07-15T16:25:00:657211 [SOURCE_CAPTURE ]T: Entering 'mysql_endpoint_free_imp' (mysql_endpoint_imp.c:778)
00008897: 2020-07-15T16:25:00:657760 [SOURCE_CAPTURE ]T: Leaving 'mysql_endpoint_free_imp' (mysql_endpoint_imp.c:795)
00008897: 2020-07-15T16:25:00:657035 [SOURCE_CAPTURE ]E: Error 2058 (Plugin caching_sha2_password could not be loaded: /usr/local/lib/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory) connecting to MySQL server '192.168.3.106' [1020414] (mysql_endpoint_capture.c:275)
00008897: 2020-07-15T16:25:00:657067 [SOURCE_CAPTURE ]E: Errors in MySQL server binary logging configuration [1020414] (mysql_endpoint_imp.c:672)
00008897: 2020-07-15T16:25:00:657092 [TASK_MANAGER ]E: Failed while preparing stream component 'st_0_ovm106-MySQL8-S'. [1020414] (subtask.c:825)

Regards,