Troubleshooting connections to data sources may require tracing data traffic to reveal the communication patterns and details between a client and the database server.
For a more generic troubleshooting guide, see Troubleshooting Data Connections in Qlik Cloud and Qlik Sense Enterprise on Windows.
We advise to first narrow down the issue as much as possible. If the load script of the .qvw / .qvf contains a lot of statements it helps a lot if a smaller document can be created, one which contains only the problem statements.
ODBC connections are most commonly configured through Windows, which means that the connection can be traced through Windows. For more detais on ODBC tracing, please see Troubleshooting Qlik products: Generate an ODBC Trace with ODBC Data Source Administrator.
OLE DB based tracing is based on the the database driver provider. The tracing is done differently depending on the database system. Please see below for reference to tracing of most common databases:
Microsoft SQL Server: http://msdn.microsoft.com/en-us/library/ms971550.aspx
Oracle Database: http://www.emigar.com/wiki/index.php/Oracle_client_trace
IBM Database: http://www-01.ibm.com/support/docview.wss?uid=nas8N1013283
In addition, enable QVConnect logging:
Troubleshooting Qlik products: QVConnect logging
Related Content
Troubleshooting Data Connections in Qlik Cloud and Qlik Sense Enterprise on Windows
Troubleshooting Qlik products: QVConnect logging
Troubleshooting Qlik products: Generate an ODBC Trace with ODBC Data Source Administrator
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
