Qlik not compiling

[alexpanjhc]

I have this program that i have been working on and today suddenly it stopped compiling.

It is when I hit the reload button, this file just sits there. Usually it took a couple of minutes and screen freeze a bit and then it reload, but now it just hang and then without any signs, it stopped as if it never ran. It also created some tmp file in the same location and that tmp file did not remove itself---usually it will after finished compiling.

I wonder if you have seen this before?

Thanks all!

[Anonymous]

Yup, can be due do :

1. Cartesian Join
2. Huge synthetic key being generated
3. A file lock

Try reloading just a few rows in Debug mode, often helpful in diagnosing 1 & 2 above.

For 3, if you can't find offending lock then reboot your computer.

[Oleg_Troyansky]

Hi Alex,

have you tried running a Limited Load via the Debugger, just to see how the data model looks like at the end?

Cheers,

Oleg Troyansky

Upgrade your Qlik skills at the Masters Summit for Qlik - coming soon to Milan, Italy!

[HirisH_V7]

Hi,

It may be due to any data base connection problem and how big is your tables and how many synthetic keys you have in your application, Make sure the synthetic keys should be min and try to avoid date and time in one field,it takes a lot of memory.

See also the log file where exactly it is failin enabling log file in document properties.

Is there any error popping up!!

Windows Task to Restart QDS.docx

HTH,

Hirish

[alexpanjhc]

Hi Oleg

I tried partial load and reduced data load, it is the same.  I do not believe i have synthetic keys because this worked fine earlier and I just dropped a couple of unused fields to reload.

[Anonymous]

I'd suggest putting the fields you dropped back.  They may have changed a good join into a cartesian join.

If one does a change and then things go bad, the change should always be a suspect.

[alexpanjhc]

Bill,

so here is the 3-layer structure we are using.

1 first layer of generating the QVDs

2nd layer of getting the data model.

3rd layer UI

The first and 2nd layers are all fine and the 3rd layer is a binary load to get the 2nd layer's qvw. I think that if anything happens with the join, it would stop at the 2nd layer. Yes?