Tshared file keeps breaking the App (high CPU)

[OliverF]

Hi,

I am facing a weird issue. One of my apps produces very high CPU usage and is almost not usable anymore. I found that this issue is often related to a broken *.tshared file. I deleted that file and everything runs smooth again.

My problem is, that this only lasts for a +- a day. Then the problem is back and I can solve it again by deleting *.tshared.

Is this a known issue? Is there a solution for this? We have already updated to the latest QlikView version.

[rubenmarin]

Hi! It’s been quite a long time since I last worked on a QlikView server... here you have more info about the tshared files:

https://community.qlik.com/t5/Official-Support-Articles/Shared-Files-General-Information/ta-p/171197...

https://community.qlik.com/t5/Official-Support-Articles/Shared-Files-Detecting-Corruption-in-the-Env...

You can try disabling or limiting the users that can create user objects to confirm if the stability increases, knowing the cause of performance degration can help to find a more precise solution.

https://community.qlik.com/t5/App-Development/QlikView-preventing-user-from-creating-new-sheets-obje...

[marcus_sommer]

Additionally to the hints from @rubenmarin you may take a few snapshots from the tshared-file - after it's re-created to the point of not working anymore. And then looking to the number of records over all as well as for certain parts - maybe there is any pattern visible and/or other strange irregularities.

Beside this take a look if any automatism are applied like OnOpen/OnSelect or whatever actions which may fire very often to permanently and also to the data-model ensuring that there are no synthetic keys or circular loops or calculations/selections against island-tables (cartesian calculations may be attempted by combining bookmarks or any dynamic dimension/measures control).

[OliverF · Accepted solution]

Hi,

good news: I solved the issue. - But it was a completely different problem than I thought.

Turned out the source data had a problem resulting in a link table that had millions instead of thousands entries. - So far so good. Very obvious explanation.

But I really don't understand why the app with the million-links works well when deleting the tshared file. This is a really weird behavior of Qlik View.

[marcus_sommer]

I wouldn't say it worked well else the mistake wasn't obvious unless any user interaction de-selected certain restrictions to the available sub-set of data respectively activated sheets/objects which use any calculations based on the dimensionality-linking of this table - which might be also recorded to the tshared-file.

[jamescarter]

I’ve recently started paying more attention to the details when comparing online pokies.
Payment methods and responsible play information are things I usually check first.
I came across Pokies Australia while looking into these topics.