When working with Data Gateway - Direct Access, odbc drivers can have unexpected behaviors that can lead to crashes.
Note: For more information about how to enable dump file creation and Isolation capability for Data Gateway - Direct Access, please review the links included in the "Related Content" at the end of this article.
One known reason to cause crashes is the use of malformed SQL query statement.
Resolution
After configuring the dump file generation and Process Isolation, dump files will be created under the folder configured during the setup.
Once a crash occurs the file will include the process id associated to the reload:
dotnet.exe.XXXXX.dmp
Where XXXX will be the process id.
With that process id and looking for the date and time when the file was created, in the odbc connector log, is possible to find the ProcessId associated to the Id of the dump file and get the reload ID.
Once the reload id was identified, from the QMC get the reload script associated to the reload id to verify the query that was triggered.
If the query is executed from a third party tool (outside of Qlik products) and doesn't work, the problem is a malformed SELECT statement.
If the issue is not related to a malformed SELECT query, collect the dump file and contact Qlik Support for further analysis.
Cause
Malformed SQL query statement.
Related Content
Mitigating connector crashes during reload
How to collect dump files for the Qlik Data Gateway - Direct Access ODBC connector crashes.
Environment
- Data Gateway - Direct Access
