Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
riishabhz
Creator
Creator

script gets strucked and doesnt load

hello everyone and @rwunderlich

please look at my script :-

material:
LOAD MATERIAL,
COLOR,
SIZE,
[Size Group],
Description,
COMPOSITION,
BRANDCD,
BRAND,
SEASON,
SEASONDESC,
THEME,
DELYCODE,
GENDER,
ProductHierarchy,
MaterialGroup,
[Core/Fashion],
FIT,
PATTERN,
[Key/NonKey],
RANGE,
ORIGIN,
[Top/Bottom],
SLEEVE,
NECK,
WEATHER,
OCCASSION,
CustomDesc,
MaterialGrp4,
MGRP4DESC,
EAN,
ALTEAN,
PurchaseGroup,
PurchaseGroupDesc,
CATEGORY,
SUBCAT,
BASECOMP,
MaterialType,
ValuationClass,
COST,
MRP,
ChangeDt,
RowNo() as RecId
FROM
[C:\Users\dmsadmin\Desktop\riishabhz\New folder\MAT_MAS\material\MAT_MAS_*.txt]
(txt, codepage is 1252, embedded labels, delimiter is '|', msq) ;

Inner Join(material)
LOAD EAN, Max(RecId) as RecId
Resident material
Group by EAN;
DROP FIELD RecId;


NoConcatenate
table1:
load * Resident final;    // final is table of sql incremental , i cant post full script as it would be too long to read .
Concatenate(table1)
LOAD* Resident final1; // final1 is also incremental sql table 
Join(table1)
load * Resident material ;  // problem arises here because i have 28 files of txt format so i have loaded all by  using *, but qlikview gets strucked when it loads only first file and doesnt respond, please help. 
DROP Table final,final1,material;

6 Replies
DavidM
Partner - Creator II
Partner - Creator II

Hi,

most likely it is problem with join (check the names of the fields) - or the data is too large and your RAM can't handle it

riishabhz
Creator
Creator
Author

data is only of 500mb so i dont think its too heavy to handle

DavidM
Partner - Creator II
Partner - Creator II

Check your RAM usage while running the script - join takes lot of RAM. The mistake might be there is no common field and Qlik does cartesian join - this is very demanding (I was once joining two tables with about 20mil rows, and one typo lead to caresian join which would create 400mil rows - 32GB  RAM couldn't handle this).

riishabhz
Creator
Creator
Author

ok sir, how to handle this any solutions ?

DavidM
Partner - Creator II
Partner - Creator II

use first 100 load or limit your load in debugger and check whether the joins are happening correctly. If no, fix the mistake. If the joins the data is being loaded correctly and everything works without being stuck, then you have insufficient RAM.

riishabhz
Creator
Creator
Author

Ok sir, will try it