Qlik Community

QlikView Connectors

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

Not applicable

QVX_UNEXPECTED_END_OF_DATA Issue

Hi ,

Can anyone Please help me resolve this issue, which i am getting while Refreshing an Application, every alternate day. It's following a weird pattern and not sure what could it be pointing to.

Checked the SAP Connector settings with BASIS team and all seems to be fine from their end.

7/22/2014 3:20:10 PM:       QVX_UNEXPECTED_END_OF_DATA:

7/22/2014 3:20:10 PM:       Error: Custom read failed

7/22/2014 3:20:10 PM:       General Script Error

7/22/2014 3:20:10 PM:       Execution Failed

7/22/2014 3:20:10 PM:      Execution finished.

Can someone, pls give some tip's to resolve this ??

13 Replies
jaimeaguilar
Valued Contributor II

Re: QVX_UNEXPECTED_END_OF_DATA Issue

Hi,

It may be happening because the volume of data you're fetching is quite big. Try splitting your data extraction into several QVDs and then in a later step you can merge all of them,

regards

Not applicable

Re: QVX_UNEXPECTED_END_OF_DATA Issue

Hi jamie,

However why is it that it's following a pattern?? It ran perfectly fine yesterday but it's every other day that it shows a failure..Also it's an incremental load that we are doing..

yfe
Contributor III

Re: QVX_UNEXPECTED_END_OF_DATA Issue

Hi Aprurva

Please upload the the SAP connector log and we will be able the exact problem...

Thanks

Yaniv

Not applicable

Re: Re: QVX_UNEXPECTED_END_OF_DATA Issue

Hi..Attached the SAP Connector Log for today.. I have been getting this offlate only..

No changes with respect to permission's or on SAP side have been done..

I checked with the Basis administrator too and this the information I received.

Buffersize_kb = 200,000

Max_objects = 10,000

jaimeaguilar
Valued Contributor II

Re: QVX_UNEXPECTED_END_OF_DATA Issue

I've seen that error when I try to extract a lot of data in a single extraction. The workaround that I've found is to split extraction in smaller QVDs. However, it can also depend on other factors like bandwidth at the moment of the extraction or other processes doing something with the DB at the same time QV is extracting data.

Also when I've seen this error, it happens randomly, so what you say it's pretty weird about the pattern you've detected.

Like Yaniv said the best way to help you better is to take a look at the connector log

Not applicable

Re: Re: QVX_UNEXPECTED_END_OF_DATA Issue

Thanks Jamie.. yes splitting would be one option that we would try doing in our lower environments.. however

Would it be useful to check these points with the Basis team again??

  • The error is related to missing export / import shared buffer on the SAP system. This should be checked by the SAP Basis Administrator. Mostly there are other SAP Jobs running blocking the connector to read the data.??
  • TimeOutFetch Paramete in SAP Connector connection String??

I was just browsing through some old post's and we might want to check these, but I am not that experienced from SAP side, hence need your inputs to proceed further..

yfe
Contributor III

Re: QVX_UNEXPECTED_END_OF_DATA Issue

Hi Apurva

I looked at the log file.

Instead of writing all the fields for extraction, please try the following simple command:

SQL SELECT *

FROM /BIC/AZSA_D_1100 WHERE SYSPRCBEG  > '20140722033223'

Thanks

Yaniv

Not applicable

Re: Re: QVX_UNEXPECTED_END_OF_DATA Issue

Hi Yaniv.. Ok would execute that, and also just a point that its a 6 GB QVD..

Also, can the below be the possible reason's by any chance??

  • The error is related to missing export / import shared buffer on the SAP system. This should be checked by the SAP Basis Administrator. Mostly there are other SAP Jobs running blocking the connector to read the data.??
  • TimeOutFetch Paramete in SAP Connector connection String??
yfe
Contributor III

Re: QVX_UNEXPECTED_END_OF_DATA Issue

Hi Apurva

6 GB is a big size... However, I would expect the SQL connector to handle it because it works with packets in a background job - which means memory allocation is handled properly in SAP/BW (I conduct large extractions without any problems).

Regarding your questions - I am not sure. In order to verify - please try to extract a small amount of data from that table (i.e. hundreds of records, not more). If the extract fails - it would require further investigation.

Moreover, please send the connection string that you use

Thanks

Yaniv