Skip to main content
Announcements
Global Transformation Awards submissions are open! SUBMIT YOUR STORY

Qlik Data Gateway - Direct Access - ODBC Crashes

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

Qlik Data Gateway - Direct Access - ODBC Crashes

Last Update:

Nov 27, 2024 8:09:14 AM

Updated By:

Sonja_Bauernfeind

Created date:

Nov 27, 2024 8:07:47 AM

When an ODBC connector crash occurs in Qlik Data Gateway — Direct Access, other concurrent reloads may be impacted following the original crash. This will specifically be the case if Process Isolation is not enabled. 

To verify if there are ODBC connector crashes:

  1. Go to the DAG (Direct Access Gateway) folder: C:\Program Files\Qlik\ConnectorAgent\data\logs\
  2. From there, use any file search tool and search for “has exited” entries in the DirectAccessAgent log files, an example:

    [Manager ] [WARN ] ODBC process (2172) has exited (exit code: 0), going to restart it...

Multiple connector crashes can have a big impact on the stability of the Direct Access Gateway. 

Resolution

Enable Process Isolation as documented in Mitigating connector crashes during reload

Cause

Some crashes can occur due to malformed queries, refer to the Data Gateway - Direct Access. Initial validation for ODBC crashes article.

If there are other crashes without traces that could explain their nature, enable dump file creation, collect the dump files and necessary information for DAG cases and contact Qlik Support. 

 

Environment

  • Qlik Cloud
  • Qlik Data Gateway - Direct Access
Labels (1)
Version history
Last update:
‎2024-11-27 08:09 AM
Updated by: