topic Direct discovery problem in QlikView

Direct discovery problem

Fri, 30 May 2014 03:30:31 GMT

It appear the following problem . It isn't always appear How to solve this prolem ?

Re: Direct discovery problem

Fri, 30 May 2014 03:34:08 GMT

the attached pic

Re: Direct discovery problem

SergeyMak — Fri, 30 May 2014 04:41:08 GMT

Hi, Jack

Did you try to see what is happening with memory via task manager?

Re: Direct discovery problem

Clint_Carr — Fri, 30 May 2014 04:45:39 GMT

Hi Jack,

What are the system resources of your database server? Is their sufficient disk space?

The logging available to Direct Discovery is by way of ODBC logging.

Direct Discovery SQL statements passed to the data source can be recorded in the trace files of the database connection. For a standard ODBC connection, tracing is started with the ODBC Data Source Administrator:

Can you enable logging and post the results?

Clint

Re: Direct discovery problem

Sat, 31 May 2014 08:40:46 GMT

My server memory is 256GB , My file log is as following:

(2014-05-31 12:40:04) Information: The Source Document reload complete. DocumentPath=F:\BI\DEPLOY\STOCK.qvw

(2014-05-31 12:40:04) Information: Memory Allocation Delta for this file=435.48 Mb. Available Physical Memory Before Reload=371818.34 Mb. Available Physical Memory After Reload=373737.98 Mb. Total Physical Memory=373737.98 Mb.

(2014-05-31 12:40:04) Error: The Source Document was NOT reloaded successfully. DocumentPath=F:\BI\DEPLOY\STOCK.qvw.

(2014-05-31 12:40:04) Information: Closing the document.

Re: Direct discovery problem

Sat, 31 May 2014 08:49:55 GMT

I try many methods :

1 I load it in two client computer (the server is the same) . It isn't ok.

2 Sometimes ,it can be reloaded .

3 I have two server with 70% memory used, One is ok ,another isn't ok.

4 Today I load ok because of the server load is low.

I want to know which factors affect the DD .

Re: Re: Direct discovery problem

Sun, 01 Jun 2014 13:41:12 GMT

Today I run twice . One fail . The attachment is the log file on OMC. The third times reload too long and the SQLlog is more 1.9GB .

Re: Direct discovery problem

antoniotiman — Sun, 01 Jun 2014 14:21:21 GMT

Hi Jack,

have You tried to update ODBC Driver of MySql (5.1) ?

Regards,

Antonio

Re: Direct discovery problem

Mon, 02 Jun 2014 00:20:16 GMT

I am using mySQL3.51. I find there are data format problems using 5.1 when using QV SQL SELECT .

Re: Direct discovery problem

Mon, 02 Jun 2014 00:21:54 GMT

SORRY , MYSQL5.2

Re: Direct discovery problem

antoniotiman — Mon, 02 Jun 2014 07:00:52 GMT

I don't have problems with MySql (ver 4 and 5).

You can try to analize the query QV doing to MySql (with Monitor MySql)

and try the same query directly to MySql.