Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
gerrycastellino
Creator III
Creator III

general script error on store command

'General Script Error'  being thrown on a store command from a section of code below

When I reduce the r

Record loads to 10M  records for this assetdetail table it works fine.

On a full load - it has 31M records.

There are no other locks that I know on this table.

I have deleted and regenerated all QVD files.

Put in sleep(5000) statement, and SET ErrorMode=0;

This was work as of yesterday,  not sure why all of a sudden this is now happening.

See also log files and qvw files.

/////////////////////////////////////////////////////////////////////////

LET vAudienceSizingTableName_TEMP= 'AudienceSizing_TEMP';
LET vAudienceSizingTEMPQVD=  vBaseDir & 'QlikView_QVD\$(Folder)\$(QVDType)\$(Folder).$(QVDType).$(vAudienceSizingTableName_TEMP).qvd';

SET ErrorMode=0;

NoConcatenate

$(vAudienceSizingTableName_TEMP):

LOAD

  %Record_Counter,

  marketo_id_key,

  sfdc_contact_id_key,

  %marketo_id_key_Activity,

  %email_key,

  %sfdc_contact_id_key_AssetDetail

FROM [$(vAudienceSizingQVD)] (qvd);

Left Join

LOAD

  %email_key,

  reportclassification

FROM [$(vTauonlineuserQVD)] (qvd);

Left Join

LOAD

  %marketo_id_key_Activity,

  E_NewsletterEngagement,

  ER2BH

FROM [$(vTactivityQVD)] (qvd);

Left Join

LOAD

  marketo_id_key,

  E_TrialEngagement

FROM [$(vTsupplementalusageQVD)] (qvd);

left Join

LOAD

  %sfdc_contact_id_key_AssetDetail,

  E_SubsEngagement

FROM [$(vTassetdetailQVD)] (qvd);

//error seems to be at this store syntax

//works fine if I limit record load to 10M (out of total of 32M) records from the assetdetail QVD file

sleep(5000);

store $(vAudienceSizingTableName_TEMP) into $(vAudienceSizingTEMPQVD);

sleep(5000);

DROP table $(vAudienceSizingTableName_TEMP);

1 Solution

Accepted Solutions
Gysbert_Wassenaar

My guess is that you're running out of ram then. Try a machine with more ram. You could also try replacing the left joins with the use of mapping tables and the applymap function. Perhaps that has a positive effect on the amount of ram used.


talk is cheap, supply exceeds demand

View solution in original post

4 Replies
Gysbert_Wassenaar

Make sure your machine isn't running out of memory or disk space.


talk is cheap, supply exceeds demand
gerrycastellino
Creator III
Creator III
Author

I have plenty of disk space.

RAM  usage is at 99% at time of failure.

It runs for about 10 minutes at the store statement and then fails.

Gerry.

Gysbert_Wassenaar

My guess is that you're running out of ram then. Try a machine with more ram. You could also try replacing the left joins with the use of mapping tables and the applymap function. Perhaps that has a positive effect on the amount of ram used.


talk is cheap, supply exceeds demand
gerrycastellino
Creator III
Creator III
Author

Gysbert:

That approach seems to have worked !

Tell me where to send the box of chocolates !

Gerry.