topic Re: Sql QVX_UNEXPECTED_END_OF_DATA laod conditional. in QlikView

Sql QVX_UNEXPECTED_END_OF_DATA laod conditional.

fdelacal — Mon, 19 Nov 2012 11:43:21 GMT

Hello,
I need some help.
I have the following error QVX_UNEXPECTED_END_OF_DATA.
i was reading in the community and saw that is because the tables are very large.

I need to load 10,000 lines of

distinct load *;
sql select first 10 000
from mytable
where ab_ad = abf_ad

then I need to join this table from 10,001 to 20,000 and so on until all lines have the table. (nose few lines have the table)

any idea how to do this?

Re: Sql QVX_UNEXPECTED_END_OF_DATA laod conditional.

Mon, 19 Nov 2012 12:11:00 GMT

Hi there,

To be honest, there should be no need for you to do this. I have a QV dashboard which is loading in 96 million rows of data in one hit. I would look at your script and check for missing semi colons, as this is what the error seems to be pointing at, ie it's looking for more stuff because you haven't told it to end looking for anything because there is no semi colon.

Kind Regards,

Miles

Re: Sql QVX_UNEXPECTED_END_OF_DATA laod conditional.

fdelacal — Mon, 19 Nov 2012 12:35:31 GMT

that´s an example the real script is this,

STOCK:

load Distinct

SQL SELECT

empr.cve_amb,

empr.char2_al,

prove.cif_pro,

prove.raz_pro,

galart.mar_art,

galart.art_amb,

galart.ref_art,

galart.ctl_art,

galart.dep_art,

galard.char7_al,

galard.crs_art,

galard.dec4_al,

galard.dec5_al,

galard.dec6_al,

galard.sre_art,

(galard.sre_art - galard.crs_art)* galard.dec4_al as calculada,

galard.cod_art,

galard.cod_del,

galard.cod_Ent,

galard.cod_uea_st,

galartv.cuea_tvl,

galartv.pre_tvl,

marca.nom_mar,

marca.cod_mar

FROM

PUB.gmempr empr,

PUB.gmprove prove,

PUB.galardel galard,

PUB.galartic galart,

PUB.galartvl galartv,

PUB.galmarca marca

where

galard.cod_Ent = empr.cod_ent

and galard.cod_del = empr.cod_del

and galard.art_amb = empr.art_amb

and galartv.art_amb = galart.art_amb

and marca.cod_mar = galart.mar_art ;

in database example work fine, the problem is in the real database.