Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
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: 
Not applicable

Field not found when a lot of data

Hi,

Does anyone know why application works correctly when I load one amount of data (around 1,5 M records from SQL). And when I try to load a bit bigger amount I receive error "Field not found" with first field from my SQL script?

The script:

SET ThousandSep=' ';

SET DecimalSep=',';

SET MoneyThousandSep=' ';

SET MoneyDecimalSep=',';

SET MoneyFormat='# ##0,00 zł;-# ##0,00 zł';

SET TimeFormat='hh:mm:ss';

SET DateFormat='YYYY-MM-DD';

SET TimestampFormat='YYYY-MM-DD hh:mm:ss[.fff]';

SET MonthNames='sty;lut;mar;kwi;maj;cze;lip;sie;wrz;paź;lis;gru';

SET DayNames='Pn;Wt;Śr;Cz;Pt;So;N';

ODBC CONNECT TO pcmd;

LOAD "allocated_service",

    "answer_time",

    hour("answer_time") as ans_h,

    "call_date",

    "call_established",

    "call_type",

    cfc,

    "cfc_qualifier",

    "cfc_qualifier_sec",

    "elapsed_time",

    esn,

    "incoming_number",

    "originated_digits",

    "subscriber_number";

SQL SELECT "allocated_service",

    "answer_time",

    "call_date",

    "call_established",

    "call_type",

    cfc,

    "cfc_qualifier",

    "cfc_qualifier_sec",

    "elapsed_time",

    esn,

    "incoming_number",

    "originated_digits",

    "subscriber_number"

FROM pcmd."public"."npcmd_1210"

where "call_date" between '2012-10-18' and '2012-10-31';

When the above date range starts from 2012-10-20 it works fine. When the range is between 18 and 22 it works fine as well. But when the range is wider like in the example it returns error.

Does the QlikView have any data size limitation?

Jacek

1 Solution

Accepted Solutions
Not applicable
Author

Problem solved!


It was not QV fault. The problem was option "Use Declare/Fetch" in the PostgreSQL ODBC driver.

When this option is disabled it behaves like in my first post. When enabled all the data loaded successfully.

View solution in original post

5 Replies
Not applicable
Author

Hai,

do u have any idea about that count of records

Not applicable
Author

Yes.

For dates range 18-31/10/2012 it is 1856622 records.

For dates range 20-31/10/2012 it is 1549583 records.

For dates range 18-22/10/2012 it is 602053 records.

So it is around 150000 per day.

Oh, the same situation is with completely different database and different SQL script. Over som amount of loaded data I get that eror.

chematos
Specialist II
Specialist II

Have you check if there is an overload of the RAM memory while loading data?

Not applicable
Author

Yes, I have total of 2GB memory. And during data loading task manager shows free memory all the time above 600MB so it is not memory problem.

Not applicable
Author

Problem solved!


It was not QV fault. The problem was option "Use Declare/Fetch" in the PostgreSQL ODBC driver.

When this option is disabled it behaves like in my first post. When enabled all the data loaded successfully.