Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
ansarz2601
Contributor II
Contributor II

How to read the Qlik-Impala ODBC logs with TRACE Enabled

Hi All, 

 

Needed assistance on understand the Qlik-Impala ODBC native logs. we are facing some issues when Qlik is connecting to Cloudera Big data Cluster for which we have enabled TRACE on QLIK and extracted logs. But we are unable to read/understand the logs. 

Please help us in understanding the logs to check with the issues.

 

Thanks, 
Ansar.

6 Replies
petter
Partner - Champion III
Partner - Champion III

Could you be more specific please:

1. Exactly where and how did you enable trace in the first place.

2. Unable to read ... means? Didn't you find them?

3. What didn't you understand in the logs. Do you have a snippet of the log that you could show us?

4. Which version of Qlik Sense did you use?

5. Which version of Cloudera Impala are you running on the server side? 

ansarz2601
Contributor II
Contributor II
Author

Hi Petter,

Appreciate your assistance on this. Please find the answers in line to this reply.

 

1. Exactly where and how did you enable trace in the first place. :

(ANS) : Followed the steps in the link mentioned here https://support.qlik.com/articles/000055332

Configure the ODBC tracing mode: If it is necessary, log on using an account that has membership in the Local Administrators' group.

From Administrative Tools, open the ODBC Data Source Administrator.

Click the Tracing tab.

Configure the tracing mode using the Machine-Wide tracing for all user identities check box:

To enable machine-wide tracing, select the check box.

To return to per-user tracing, clear the check box.

Click Apply.

2. Unable to read ... means? Didn't you find them?

(ANS) We have found them and extracted but unable to understand the logs.

3. What didn't you understand in the logs. Do you have a snippet of the log that you could show us?

(ANS) Attached are logs.

4. Which version of Qlik Sense did you use?

(ANS) November 2017 (3.2)

5. Which version of Cloudera Impala are you running on the server side?

(ANS) 2.12.0 + CDH 5.16.2

ansarz2601
Contributor II
Contributor II
Author

Hi Petter, 

Hope you doing well. 

Did you get any chance to look for the below mentioned query? Appreciate if you can assist me on this. 

 

Thanks, 
Ansar

petter
Partner - Champion III
Partner - Champion III

You say that you are "having some issues" ... could you be more specific to exactly what the isusses are?

I did have a look at the log though - and within it it was some error messages which contained the string "br3akThr0ugHc0NN3ct1v1TY"

 

This knowledge article sugges that you should possibly upgrade to a Qlik Sense of April 2018 or later:

https://support.qlik.com/articles/000050005

 

 

ansarz2601
Contributor II
Contributor II
Author

Hi Petter, 

 

So here is a detailed explanation on what I am looking for : 

 

We have connected Qlik with Qlik ODBC through Impala. And when there is a scheduled query run from Qlik, it gets queried on our cloudera cluster. However, the same query is getting failed with the error session timed out. We checked with Cloudera Team and Application, there is no issue within Cloudera. 

 

Cloudera Team advised to get connected with Qlik Team to know about the logs as we were unable to understand the logs. we wanted to understand how did the queries fail, but a same query was automatically generated and executed. wherein Qlik fired the query only once. 

 

The issues we are facing is, we are not understanding the logs, as we are not from Qlik and Qlik team here says that the issue do not persists as they are getting the data. 

 

But we wanted to understand, why this is happening. 

 

Let me know if you need any more details please.

 

Thanks, 
Ansar.

petter
Partner - Champion III
Partner - Champion III

I think what the knowledge-base article says is the best remedy to your problem. Upgrade to a newer Qlik Sense Enterprise.