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

Announcements
Join us in Bucharest on Sept 18th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Reload process hangs after executing the last commands

We use QV 11.20.12742.0 SR12 Local Client for 1 User on a Microsoft Windows Terminalserver 2008 R2 (first installed just yet).

The application runs very well, but the reload "hangs". The reload-process loads about 7 minutes, then you see, that the last command is executed. After that, the reload-window does not Close and we have 6% CPU ulilization "forever".

The Skript seemed to be ok, because it runs on an older QV-Version and an older Server (32-Bit) many years.

What can we do?

1 Solution

Accepted Solutions
Not applicable
Author

Thanks for your support. The Skript contains RESIDENT-commands which are not caused a problem in the older Version (V5) but now in V11. After removing these commands and redesign the skript the problem is fixed.

View solution in original post

6 Replies
prieper
Master II
Master II

Did you check the "Close"-Tickmark in the script-screen?

Peter

Not applicable
Author

Yes, of course.

The counter stops after 7 Minutes, so you can see, that the exucution of the script is finished, but the window does not Close and the CPU-utilization is still there and you can wait forerver...

PrashantSangle

Hi,

Test Reload using Debug and Limit Load.

Do you have any synthetic key or Circular Loop inside it???

Regards

Great dreamer's dreams never fulfilled, they are always transcended.
Please appreciate our Qlik community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
prieper
Master II
Master II

Does it have same behaviour with limited amount of data?

Are there some extensive joins in the script? synthetic keys? do the keys have same datatype (integer vs decimals)? what does the log say?

But CPU-utilization points to huge cartesian products (synthetic keys) - this would be the first address.

If running locally (not reload via server), would then also check for extensive open tables.

Peter

hannan_t
Partner - Contributor III
Partner - Contributor III

This normally happens when you have synthetic keys being created in the script. Try loading the data through limited load/debugger and analyse if there are any synthetic keys being created. Uncheck the "Close" so that you can see at the end of reload if there are any synthetic keys being made.
If there are synthetic keys then you will have to optimize your script and get rid of as many synthetic keys as possible (ideally zero).

Not applicable
Author

Thanks for your support. The Skript contains RESIDENT-commands which are not caused a problem in the older Version (V5) but now in V11. After removing these commands and redesign the skript the problem is fixed.