Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi, I have in error when I connect to table (other table from data base was ok).
I forwarded it to people from the data source following the example of this topic: link
In response, they asked me to prove that it was not a mistake on Qlik's part - how could I prove it?
My Qlik version is: May 2024 Patch 3 / qliksenserver 14.187.7
In a similar period to the error occurred, we upgraded Qlik from version 2022, but I doubt that upgrading the version caused the problem because we have several connections, a lot of tables and everything except this one works fine.
Comparing the queries and the tables from the working ones against the failed one may give some valuable hints which fields/processing/data doesn't fit to the specified data-types. Further reducing the load to 1 / 3 / 10 / n fields and/or rows should be also return insights. Another approach could be to enable or to extend the logging of the driver and the data-base to get a more detailed error-message.
Similar topics with explanation:
Solved: CLOB conversion to varchar - Qlik Community - 1988276
Qlik Replicate Transformation: Source Lookup - CLO... - Qlik Community - 1987353
Fast fix:
Comparing the queries and the tables from the working ones against the failed one may give some valuable hints which fields/processing/data doesn't fit to the specified data-types. Further reducing the load to 1 / 3 / 10 / n fields and/or rows should be also return insights. Another approach could be to enable or to extend the logging of the driver and the data-base to get a more detailed error-message.
Thx @marcus_sommer , I did some tests according to your suggestion:
I'm still waiting for a response from the people who manage this database, but this data is very helpful
I think it hints for a driver-issue which couldn't handle the data-type of this field properly (maybe a newer sub-type as defined within the driver) and/or there may an issue with the specified/available char-set because there are various special-chars included. Struggling with the driver could be quite exhausting - therefore any kind of cast-statement within the query might be more practically.
Similar topics with explanation:
Solved: CLOB conversion to varchar - Qlik Community - 1988276
Qlik Replicate Transformation: Source Lookup - CLO... - Qlik Community - 1987353
Fast fix: