Qlik Replicate - MySQL source defect and fix (2023.11)

john_wang — Sat, 04 May 2024 14:30:01 GMT

Upgrade installation or fresh installation of Qlik Replicate 2023.11 (includes builds GA, PR01 & PR02), Qlik Replicate reports errors for MySQL or MariaDB source endpoints. The task attempts over and over for the source capture process but fail, Resume and Startup from timestamp leads to the same results:

[SOURCE_CAPTURE ]T: Read next binary log event failed; mariadb_rpl_fetch error 0 () [1020403] (mysql_endpoint_capture.c:1060)

[SOURCE_CAPTURE ]T: Error reading binary log. [1020414] (mysql_endpoint_capture.c:3998)

Environment:

Replicate 2023.11 (GA, PR01, PR02)
MySQL source database , any version
MariaDB source database , any version

Fix Version & Resolution:

Upgrade to Replicate 2023.11 PR03 (expires 8/31/2024).

The fix is included in Replicate 2024.05 GA.

Workaround:

If you are running 2022.11, then keep run it.

No workaround for 2023.11 (GA, or PR01/PR02) .

Cause & Internal Investigation ID(s):

Jira: RECOB-8090 , Description: MySQL source fails after upgrade from 2022.11 to 2023.11

There is a bug in the MariaDB library version 3.3.5 that we started using in Replicate in 2023.11.
The bug was fixed in the new version of MariaDB library 3.3.8 which be shipped with Qlik Replicate 2023.11 PR03 and upper version(s).

article Qlik Replicate - MySQL source defect and fix (2023.11) in Official Support Articles

Qlik Replicate - MySQL source defect and fix (2023.11)

Environment:

Fix Version & Resolution:

Workaround:

Cause & Internal Investigation ID(s):

Related Content: