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

Announcements
ALERT: The support homepage carousel is not displaying. We are working toward a resolution.

Qlik Replicate shows MySQL client out of memory error while reading from a MYSQL source

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
SwathiPulagam
Support
Support

Qlik Replicate shows MySQL client out of memory error while reading from a MYSQL source

Last Update:

Apr 1, 2022 4:43:19 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 31, 2022 3:55:50 PM

As per this mysql article, the ODBC driver has to use mysql_use_result() to skip out of memory errors: https://dev.mysql.com/doc/refman/8.0/en/out-of-memory.html

Here is the ODBC parameters list and we found NO_CACHE is the listed parameter to enable mysql_use_result() for the MySQL client: https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-configuration-connection-parameters.html

You can add NO_CACHE on MySQL endpoint --> Go to MYSQL endpoint-->Advanced-->Additional ODBC connection properties.

You can see the affected parameter from the log also as below:

00019392: 2022-03-25T13:27:06:659296 [TASK_MANAGER ]I: Task Id: 7b0f52f9-358a-0a4a-aec2-eee8df5b4a01 (replicationtask.c:3779)

00019392: 2022-03-25T13:27:06:683865 [METADATA_MANAGE ]I: Driver 'MySQL ODBC 8.0 Unicode Driver' is installed and will be used (mysql_endpoint_imp.c:439)

00019392: 2022-03-25T13:27:06:683865 [METADATA_MANAGE ]I: ODBC additional properties = 'NO_CACHE' (mysql_endpoint_imp.c:496)

00019392: 2022-03-25T13:27:06:683865 [METADATA_MANAGE ]I: Connecting to MySQL using ODBC connection string: DRIVER={MySQL ODBC 8.0 Unicode Driver};SERVER=localhost;port=3306;UID=root;DB=;CHARSET=binary;initstmt=SET time_zone='+00:00';Option=74448896;NO_CACHENO_LOCALE=1;ENABLE_LOCAL_INFILE=0;sslmode=Preferred;PWD=***; (mysql_endpoint_imp.c:597)

 

Environment

Qlik Replicate 
MYSQL

 

Labels (1)
Version history
Last update:
‎2022-04-01 04:43 AM
Updated by: