Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QlikView error while creating QVD file

i have a view in my database (Oracle) and I use this view to export data to a QVD file. I use QlikView for exporting to this QVD via a QVW file, and I want to automatically run it 2 times every day.

So I put it onto a server and I scheduled it to run 2 times every day. When I run the QVW script manually, it exports the correct QVD file. However, when it is scheduled, I have an error like this in the log file:

       

     QVX_UNEXPECTED_END_OF_DATA:
     Error: OLEDB read failed
     General Script Error
     Execution Failed
     Execution finished.

i tried to run for each column (in my view) one by one. My problem is in the WHERE clause:

     select ...
     from ...
     where ...
     and ACTUAL_DATE  >= to_date(sysdate, 'dd.MM.YYYY hh24:mi:ss')

I removed this "ACTUAL_DATE >= to_date(sysdate, 'dd.MM.YYYY hh24:mi:ss')" and it runs perfectly, but when I add this clause back, I get an error.

What could I do to solve this?

22 Replies
marcus_sommer

It sounds like an issue with missing access rights to the database and/or your (network)-storage from the user under which your server runs.

- Marcus

Peter_Cammaert
Partner - Champion III
Partner - Champion III

Proceeding where Marcus left off, you could run the script again but with an alternate WHERE cause, e.g. if this:

WHERE ACTUAL_DATE >= '01.01.2014';

runs without any errors, you know that it's sysdate that's causing trouble.

Peter

Anonymous
Not applicable
Author

Could you share the whole load statement from your script ?

Gabriel
Partner - Specialist III
Partner - Specialist III

Hi,

In your WHERE clause, your date format might be wrong.

Try date as 'YYY-MM-DD'

maxgro
MVP
MVP

I would try these

1)

and ACTUAL_DATE  >= sysdate

2)

ODBC instead of OLEDB

3)

when you run the script manually, do you run it with the same user of the QlikView distrib service?

If not, maybe some settings (regional settings) are different?  

Not applicable
Author

You don't need to tell Oracle to format the sysdate.

So 'ACTUAL_DATE  >= sysdate' should suffice

Not applicable
Author

I already tried it, error is same

Not applicable
Author

my date (ACTUAL_DATE) format is 'dd.mm.yyyy'. i am sure about that. i checked each data one by one.

Gabriel
Partner - Specialist III
Partner - Specialist III

Hi,

In that case I have tried not formatting the sysdate?