Load script skips a table during the script execution process

[sinanozdemir]

Hi all,

I have been having an issue that I couldn't figure out the root cause of it. I am trying to load two tables VM_CLAIM and VM_MEMBMTHS, and they both reside in the same database so that the one ODBC connection is used. Also "Force 32 Bit" option is checked.

What happens is that the first table VM_CLAIM gets loaded, but the second table VM_MEMBMTHS doesn't. Almost QlikView skips the second table for some reasons. I checked the availability of VM_MEMBMTHS table in both SQL Server and another BI tool, the table runs perfectly.

Here is a screenshot of the script execution progress window:

There are two different tables in the load script:

I also checked if the tables are being concatenated, and there is only one common field in both tables so I don't think it is a concatenation issue.

If anyone had this issue and resolved it, I would appreciate your feedback.

Thank you

pbutterw‌

[sinanozdemir]

Sorry Andres. It didn't work. Although, it works if I only pull everything "*" without any manipulations.

Thanks

[andrespa]

No worries, it's as Peter just said. Try to do it with resident loads instead of preceding.

Best of luck,

Andrés

[sinanozdemir]

Hi Peter,

Thank you for your feedback. However, this happens with only a handful of tables. I started wondering if it is because of the table/database design. For the problematic table, there are columns like the below ones:

And these columns are just empty. They are used as headers, but I am not even bringing any of these fields though.

Thank you.

[sinanozdemir]

Thank you again Andres for your time and feedback.

[sinanozdemir]

Hi Eduardo,

it just ends, the close button is active.

Yes, I tried Noconcatenate and it didn't solve the issue.

I will go with Marcus' suggestion.

Thank you all.

[byronhuff]

Has anything been done in newer version of Qlik to alleviate this problem?

Re: Load script skips a table during the script execution process

It is commonly known (very recently by me as well, although I've been fighting them for some time now) that Preceding Loads should be used for doing just minor column and value manipulations. As soon as you start doing extra filtering (or GROUP BYs) you may unexpectedly run into trouble.

[byronhuff]

It is commonly known (very recently by me as well, although I've been fighting them for some time now) that Preceding Loads should be used for doing just minor column and value manipulations. As soon as you start doing extra filtering (or GROUP BYs) you may unexpectedly run into trouble.