Direct discovery problem

[#1]

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

[#2]

the attached pic

[SergeyMak]

Hi, Jack

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

[Clint_Carr]

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

[#5]

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.

[#6]

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 .

[#7]

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 .

[antoniotiman]

Hi Jack,

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

Regards,

Antonio

[#9]

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

[#10]

SORRY , MYSQL5.2