SAP Fetch aborted due to incorrect number of rows

[agsearle]

There was a previous discussion on this issue, but it was closed with no result.

Also the issue was supposed to have been fixed on SAP Connector 5.8 SR4. However we are on SAP Connector 6.0IR and are still having the issue on a regular basis.

When extracting data from SAP using the SAP Connector the load fails right at the end saying 'fetch aborted due to incorrect number rows', particularly for larger extracts. We are using QV11.2 SR12, and at the moment are unable to upgrade any further due to current software limitations.

Has anyone else managed to sort this issue?

[Tomas_Sommergyll]

Hi Andrew,

Is it possible to attach a log file from the folder:

C:\ProgramData\QlikTech\Custom Data\QvSAPConnector\Log

that shows the issue?

Thanks,

Tomas

[agsearle]

Here is the SAP Connector log.

[Tomas_Sommergyll]

Thanks for the log file.

There is 1 packet missing in the job but the log does not show any other issues.

How often does this issue happen?

Is it always the same query or different ones?

The next step is to look at your SAP system. Check the following:

1. Run SM37 to view the Job Overview list.

   a) Enter Job name /QTQVC/READ_DATA, your user name and the job start date, and press Execute.

   b) Select (double-click) the Job from the list.

   c) Select the Job log and read the message text. Does it show any errors/warnings?

2. Run SE16 with table name: /QTQVC/STATUS

   a) Enter Connector: SQL and job date/time.

   b) Select (double-click) the Job from the list.

   c) Check Jobstatus and text (total number of rows fetched). Is same as in log file?

What are the results from these checks?

Br,

Tomas

[agsearle]

This issue happens regularly, and can be on any of our loads from SAP. Usually if a job fails for this reason, it then works correctly when reloaded.

I've checked item 1, and there are no error messages there:

The second item shows the same amount of rows:

Any more ideas?

Andrew

[Tomas_Sommergyll]

Hi Andrew,

The screenshots look OK.

I suggest that you reach out to the Qlik Support team to get a more focused help with this issue. Please refer to this thread to the contact person.

In the meanwhile it is worth trying to reproduce the problem while tracing, please check the following document how to do that (the Qlik Support will ask you to reproduce the issue as the first step):

Qlik Connector for SAP - Tips and Tricks v1.5

under the section "Create and find Trace records" on p. 22.

If possible, try finding a smaller job to reduce the number of trace entries that are generated.

Br,

Tomas

[agsearle]

Thanks for your help Tomas.

I have raised the issue with Qlik as suggested.

Andrew

[dennisfassbende]

Any solution from Qlik?

I have sometimes the same issue with the Qlik Connector 6.3.

Thanks

Dennis

[Hakan_Ronningberg]

Hi Dennis,

Is it possible for you to perform a trace (when the error occurs) as decribed in the section "Create and find Trace records" on p. 22 in the document below?

Qlik Connector for SAP - Tips and Tricks v1.5

Please attach the result of the trace as an Excel file and also attach the corresponding SQL connector log.

Thanks,

Hakan

[dennisfassbende]

Hi Hakan,

this issue occurs irregular. So it´s difficult to trace.

Today everything worked fine.

Any other ideas without tracing?

Best regards

Dennis

Von: Hakan Ronningberg

Gesendet: Mittwoch, 8. März 2017 10:25

An: Faßbender, Dennis

Betreff: Re: – SAP Fetch aborted due to incorrect number of rows

Qlik Community <https://community.qlik.com/?et=watches.email.thread>

SAP Fetch aborted due to incorrect number of rows

Antwort von Hakan Ronningberg<https://community.qlik.com/people/hrg?et=watches.email.thread> in QlikView Connector for SAP - Komplette Diskussion anzeigen<https://community.qlik.com/message/1226926?et=watches.email.thread#1226926>