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

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

load script is getting stuck after loading all table rows

Hi All,

I'm having a problem in load script. While loading everything is going fine. All the lines are getting fetched. But its getting stuck after that so I have to kill the process and then start again.

Can anybody please tell me why is it getting stuck ?

Thanks in advance!!!

18 Replies
amit_saini
Master III
Master III

Kavitha,

Go to Document Properties -->General--> Enable "Generate Logfile" option and reload your application . This will create automatic log file for your application.

Thanks,
AS

Jason_Michaelides
Partner - Master II
Partner - Master II

That is because two tables with the same column names are automatically CONCATENATED (i.e. stacked on top of each other). By changing one of the column names you are causing them to be separate tables and therefore a large synthetic key is being generated at the end of the load script which is killing the machine.

When you load the second table, precede the LOAD statement with CONCATENATE (<1st table name>).

This will force the concatenation and you will have a single table with all columns aligned except the one you changed the name of.

Hope this helps,

Jason

daveamz
Partner - Creator III
Partner - Creator III

Hello,

Go to "Edit script" > Debug > Check "Limited Load" to 100 and hit Run.

After reloading limited data, see if any synthetic table is created.

In first scenario, where no changes are made to the columns name, the 2 tables are concatenated automatically, in the second scenario, if you have 2 different columns, QV tries to create a synthetic table and that's why is getting stuck.

Regards,

David

its_anandrjs
Champion III
Champion III

You can find the log file creation flag it is active of not in the

Document Properties >> General >> generate log files

See snap:-

log file.png

Check your data model may be there is synthetic keys are creation and due to that your application hags may be there are more field names are same.

And did you use error modes in the application.

eduardo_sommer
Partner - Specialist
Partner - Specialist

Try using debug instead of simply reloading. Then, in the debug screen, check Limited Load. It will suggest 10 as the number of records per table. This will be fine. Then, click in Run.

After the script execution, go to the table viewer to see if it has created the synthetic keys. In case this is the reason, follow Jason's tips, using concatenate load.

Eduardo

Not applicable
Author

Hi Jason,

I tried using limited load option but I'm facing this problem in case of limited load as well.

Jason_Michaelides
Partner - Master II
Partner - Master II

I didn't suggest a limited load...you need to use CONCATENATE

Not applicable
Author

Hi Amit,

Thanks for the reply. I have done the setting you suggested. Now could you please tell the location where I can find this log file.

Not applicable
Author

Thanks Jason. Its working with CONCATENATE option.