Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Q&A with Qlik - Qlik Cloud Migration: Questions about migrating to Qlik Cloud? Catch the latest replay!
cancel
Showing results for 
Search instead for 
Did you mean: 
rbecher
Partner - Master III
Partner - Master III

Direct Discovery in version 11.2 freezing

Got this strange behavior sometimes that the chart is not executing the direct select query (nothing in connector log file) on a document opening or if a selection has changed. QlikView Desktop is just freezing and the chart refresh cannot be canceled by clicking the red cross. I'm testing with version 11.20.11616.0 IR, has anyone same experience?

Unfortunately the Direct Discovery beta group was removed...

- Ralf

Data & AI Engineer at Orionbelt.ai - a GenAI Semantic Layer Venture, Inventor of Astrato Engine
Labels (2)
17 Replies
rbecher
Partner - Master III
Partner - Master III
Author

Hi Greg,

btw., I've created this QlikBug group here.. 😉

So, please tell Johan Bini to contact me by email: ralf.becher@tiq-solutions.de

- Ralf

Data & AI Engineer at Orionbelt.ai - a GenAI Semantic Layer Venture, Inventor of Astrato Engine
Anonymous
Not applicable

Hi,

Could you provide more info about your setup, e.g. database, script info (cleaned), data amounts?

Thank you in advance,

Best Regards,

Johan Bini

rbecher
Partner - Master III
Partner - Master III
Author

Hi Johan,

we use a custom connector (our JDBCConnector.dll) which works fine with SAP HANA (and other DBs) except in Direct Discovery.

The issues are not related to the datasources (HANA DB, or MySQL, ...) or amounts of data in the source or complexity of application (very simple). The behavior is:

- freeze on document open of already loaded document (chart with hourglass) on 32bit (not on 64bit), connector dll is not instantiated

- cancel button in chart gauge (red cross) has no reaction

- if a non Direct Discovery document was opened and reloaded before with same data source, next opened document with Direct Discovery and already loaded data is working fine for some interactions, we can track the DD SQLs for dimensions and aggregations in the connectors log file

- freeze after some interactions (selecting values in listboxes etc.), several  DD SQLs are working then freeze

- Ralf

Data & AI Engineer at Orionbelt.ai - a GenAI Semantic Layer Venture, Inventor of Astrato Engine
Anonymous
Not applicable

Hi Ralf,

Thank you for the information.

With the information from Ian Crosland sent, about the noted bug:

"In certain instances with multiple Direct Discovery charts QlikView may hang due to multiple named pipe connections being executed against the source database."

Does this seem as the case? (and to mitigate with fewer charts)

Best Regards

Johan

rbecher
Partner - Master III
Partner - Master III
Author

Hi Johan,

this is not the case. Same issues occur also with only one chart.

- Ralf

Data & AI Engineer at Orionbelt.ai - a GenAI Semantic Layer Venture, Inventor of Astrato Engine
Anonymous
Not applicable

I have done a simple direct sql to a very small table on a SQL 2008 R2 server.

QlikView hangs every time i delete records in the sql table, and when i change filter in listboxes on fields using direct discovery.

I also seams to have problems with sorting in the same listboxes when data is changed.

I'm using IR 11.20..11643.0

/Henrik

tseebach
Partner - Creator III
Partner - Creator III

I've just been testing 11.2 IR, and the stability issues seems definitely gone.

But its seems that QlikView is takes a really long time before executing the Query.

What I'm experiencing is: I do a selection in a Dimension, now QlikView hangs for 15-30 seconds, and then my chart go into "loading state" and i see the SQL server is handling the queries and after another 2-3 seconds i see the results.

So QlikView seems to do something new, right after i do a selection in my list boxes. Anyone know why?

I'm using win8 64 bit, QlikView Desktop, on a MSSQL Server AdventureWorks cube via a View (OLE DB) og ODBC to a SAP HANA.

The one datasource is 100 rows large, the other is 14 mio. Both hang equally long before executing the query.

tseebach
Partner - Creator III
Partner - Creator III

I've  just finished testing the same file on my servers. It much much faster on the server, than locally via the dekstop. The difference is larger than what I would give networking credit for, but it works very nicely on a server.