Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
punitpopli
Specialist
Specialist

QlikView Debug mode getting stuck

    Hi All,

I am running a script in debug mode and at one point of time the script is getting stuck when one of the temp table getting concatenated to the Final table and not able to proceed on this.

  • temp table records : 510K
  • Final table records : around 10M

Could you please suggest what can be done in here?

Alos, would like to know below :

Can I end the script at this point where it's stuck and load again from some other part - As far as my understanding is concern we cannot do this, but still want to know if their is any option?

P.S : The script get successfully completed in the last run for previous month.

Thanks in advance

2 Replies
Anil_Babu_Samineni

My thoughts are very weird, But give some idea too

1) Some how you have 10M 510 K Rows only for whole directory so then i don't think this is the big deal to handle. Off course, There could be bulk reasons to achieve this if you provide information density and Subset ration of Primary key where Final and Temp Table?

2) Can you cross check the issue at what time you are getting debug stuck? And take Log file for that and see how log file looks and where takes the time to check for doc log

3) Off course, If we abort the script and absolutely it is not done full reload due to abort So then i could request you to check the file index using QVGD to know the completion of fulfill reload in your application


Does it make sense?

HTH

Anil

Flipkart

Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful
marcus_sommer

Not each single load-step will be displayed/logged if they contain things which need multiple steps like aggregation-loads which at first grouped the query and then calculate the aggregation and from all those steps you will only see the last step which is the writing the final data into a table. And those multiple steps could last some time and while it looked as happened nothing.

Directly end a script and start it again on this point isn't possible but by setting stopp-point and by executing the script step by step you could get a quite similar behaviour. Further it could be very helpful to move various script-tabs and using exit script; and to comment various parts to execute only certain parts of the script.

- Marcus