Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Qlik Community! 👋
We recently updated our MySQL database to version '11.4.5-MariaDB-log', and since then, all of our Qlik extractions are failing. Has anyone else encountered a similar issue after a MySQL update?
I'm getting [ERROR [HY000] [Qlik][MySQL] Unknown system variable 'max_execution_time'].
Any insights or suggestions on how to troubleshoot this would be greatly appreciated! We're using Qlik Cloud.
Thanks in advance for your help! 🙏
Hi @Jose_Badillo,
That error looks to be what Qlik is receiving from the source, so not a Qlik error per se. See thread https://community.qlik.com/t5/Connectivity-Data-Prep/qlik-cloud-mariadb/td-p/1824355, which suggests to use the open source Mariadb connector (MariaDB Connector - Latest Version) and install it as a DSN connector.
Best Regards
Greetings,
I’m encountering the same issue with version '11.4.5-MariaDB-0ubuntu0.24.10.1'. As @Chip_Matejowsky pointed out, this is a database error since Qlik Cloud is requesting the variable 'max_execution_time', which does not exist in MariaDB 11.4.
I understand that the solution proposed by @Chip_Matejowsky involves setting up a DSN (Data Source Name), but I’m unsure how to implement this in Qlik Cloud. I’d appreciate it if @Chip_Matejowsky or someone from the team could clarify the steps or suggest an alternative workaround to prevent Qlik Cloud from requiring this variable in MariaDB.
On my end, I’ve confirmed that the variable is not referenced anywhere in my SQL query. In fact, when I run the query directly on the database, it executes without issues. However, Qlik Cloud seems to automatically include it at some point in the process, though I’m not sure why.
For context, I’ve attached the full error message, which shows that my query doesn’t call this global variable, yet Qlik Cloud implicitly adds it:
Any insights on how to resolve this or configure Qlik to ignore this variable?
Thanks in advance!
Hi,
To create a DSN to use with Qlik Cloud, you can leverage Qlik Data Gateway - Direct Access.
As mentioned in earlier post, the error is coming from the source, so you could contact MariaDB support for steps to ignore variable when using MySQL.
Best Regards