Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
paul_ripley
Creator III
Creator III

QVX_UNEXPECTED_END_OF_DATA

Hello

I have an app that until recently was working with no problems.  It has now stopped working in LIVE although continues to work in TEST.  I have copied the relevant section of the log file below

17/05/2017 15:10:41: 0080    SQL EXEC  agresso.dbo.Agresso_GL_QlikView_Export_preload @startperiod = 201700, @endperiod = 201712

17/05/2017 15:10:42:          19 fields found: account, account_text, CHART, currency, cur_amount, CHARTAMT, description, dim_1, entity_text, dim_4, dim_5, portfolio_text, agresso_period, sequence_no, trans_date, voucher_date, voucher_no, voucher_type, client, 42,996 lines fetched

17/05/2017 15:11:26: 0082    STORE Agresso into [..\..\04_STAGING_DATA\S1\Agresso201700to201713.qvd] (qvd)

17/05/2017 15:11:26: 0083    DROP TABLE Agresso

17/05/2017 15:11:26: 0085  END IF

17/05/2017 15:11:26: 0092  IF vDo_eFront_DBExtract = 'Y' THEN

17/05/2017 15:11:26: 0095    OLEDB CONNECT*Provider*XPassword*

17/05/2017 15:11:27: 0098    Efront:

17/05/2017 15:11:27: 0099    LOAD

17/05/2017 15:11:27: 0100    agresso_code,

17/05/2017 15:11:27: 0101    efront_link,

17/05/2017 15:11:27: 0102    gl_account_no,

17/05/2017 15:11:27: 0103    gl_amount,

17/05/2017 15:11:27: 0104    gl_chart,

17/05/2017 15:11:27: 0105    gl_currency,

17/05/2017 15:11:27: 0106    gl_entry_description,

17/05/2017 15:11:27: 0107    gl_entry_iqid,

17/05/2017 15:11:27: 0108    gl_source,

17/05/2017 15:11:27: 0109    investee_case_number,

17/05/2017 15:11:27: 0110    investee_currency,

17/05/2017 15:11:27: 0111    investee_name,

17/05/2017 15:11:27: 0112    investor_entity_number,

17/05/2017 15:11:27: 0113    if(len(investor_entity_number)=4,investor_entity_number,if(len(investor_entity_number)=3,0&investor_entity_number,if(len(investor_entity_number)=2,00&investor_entity_number,000&investor_entity_number))) as dim_1,

17/05/2017 15:11:27: 0114    investor_name,

17/05/2017 15:11:27: 0115    investor_type,

17/05/2017 15:11:27: 0116    preload_datetime,

17/05/2017 15:11:27: 0117    ref_date,

17/05/2017 15:11:27: 0118    reporting_principle,

17/05/2017 15:11:27: 0119    tran_amount,

17/05/2017 15:11:27: 0120    tran_currency,

17/05/2017 15:11:27: 0121    Month(ref_date) as PeriodMonth,

17/05/2017 15:11:27: 0122    Year(ref_date) as PeriodYear,

17/05/2017 15:11:27: 0123    Year(ref_date) & Month(ref_date)  as eFront_period,

17/05/2017 15:11:27: 0124    if(len(IF(Month(ref_date)>3,(Year(ref_date) &(Month(ref_date)-3)),((Year(ref_date) -1)&(12+Month(ref_date)-3))))=6,IF(Month(ref_date)>3,(Year(ref_date) &(Month(ref_date)-3)),((Year(ref_date) -1)&(12+Month(ref_date)-3))),IF(Month(ref_date)>3,(Year(ref_date) &0&(Month(ref_date)-3)),((Year(ref_date) -1)&0&(12+Month(ref_date)-3))))  as efperiod

17/05/2017 15:11:27: 0126    SQL EXEC  eFront_integration.dbo.IT_Venture_GL_QlikView_Export

17/05/2017 15:11:27:          25 fields found: agresso_code, efront_link, gl_account_no, gl_amount, gl_chart, gl_currency, gl_entry_description, gl_entry_iqid, gl_source, investee_case_number, investee_currency, investee_name, investor_entity_number, dim_1, investor_name, investor_type, preload_datetime, ref_date, reporting_principle, tran_amount, tran_currency, PeriodMonth, PeriodYear, eFront_period, efperiod, 

17/05/2017 15:11:46:         QVX_UNEXPECTED_END_OF_DATA:

17/05/2017 15:11:46:         Error: OLEDB read failed

17/05/2017 15:12:05:         General Script Error

17/05/2017 15:12:06:         Execution Failed

17/05/2017 15:12:06:      Execution finished.

The error I get on screen is

 

OLEDB read failed

 

SQL EXEC eFront_integration.dbo.IT_Venture_GL_QlikView_Export

Can anyone suggest how I can work out what is causing this

Thanks

Paul

1 Solution

Accepted Solutions
paul_ripley
Creator III
Creator III
Author

Actually it wasn't a QV issue - it was rubbish data in the underlying database

View solution in original post

4 Replies
paul_ripley
Creator III
Creator III
Author

Actually it wasn't a QV issue - it was rubbish data in the underlying database

Anil_Babu_Samineni

Before moving, Can you trace the error where you got it? Could be problem with Data

Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful
paul_ripley
Creator III
Creator III
Author

Hi Anil  - thanks for your reply - it was actually a data issue.  There was text data in a numeric field

Anil_Babu_Samineni

Do you think, Whether they must have only Int or Number data type in DB. Why not in Varchar2() Datatype. Seems text along with Number can work. that's the power of Qlik. FYI only. You got answer. Good

Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful