topic some problems with QV SAP Connector 5.4 SR1 in QlikView

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 26 Jan 2026 21:26:37 GMT

Hello, friends.

I have some strange problems with the latest version of SAP Connector. Do you have something like this?

After update to the latest version my reload job is failed often, but not always.

I did some investigations and I understand that problem with getting data. My query became to return different number of rows, i.e. sometimes 'select' query return 0 rows (but I know that in the SAP table rows are exists) and sometimes return all rows (as I want).

Somebody has any ideas? why one query sometimes returns different data ?

some problems with QV SAP Connector 5.4 SR1

suniljain — Mon, 12 Jul 2010 10:37:25 GMT

Dear Friend,

With Update of latest version of SAP Coonector. You also have to update the file which is pasted in SAP Environment. otherwise New version does not work properly.

Because every version have different file set . so you have to paste the related file in SAP Environment.

Regards,

sunil Jain

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 10:43:12 GMT

Which files you mean? Do you speak about 2 SAP transports? If you mean it, I added these transports in our SAP BW system

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 10:45:59 GMT

the main problem, that SAP connector works differently and it very strange. I can't understand why my query can fetch 0 rows and after 5 minutes can get all rows from one table.

some problems with QV SAP Connector 5.4 SR1

suniljain — Mon, 12 Jul 2010 10:57:45 GMT

Dear Friend

Pls check with SAP Transaction code ST22 . wheter it shows any reason for that extraction or not. if yea, it have details for this error.

Regards,

Sunil

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 11:24:33 GMT

no, today we have no rows in ST22

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 11:27:42 GMT

and our job is finished successfully. so we can't find any error on SAP BW side. but our job return 0 rows and it's not normal, because in SAP BW we have more and more rows

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 11:29:27 GMT

and when I reload my extraction from BW after 10 minutes (for example) I can get right data with all my rows...

How can I understand such behaviour?

some problems with QV SAP Connector 5.4 SR1

suniljain — Mon, 12 Jul 2010 11:52:56 GMT

Dear Friend ,

SAP BW also works on ACID Property of RDBMS. That is Automacity, Consistency, Durability and Isolation.

When you are extracting data from SAP BW and at the same time if any communication running betbeen R/3 and B/W . At that time it gives you 0 records.

Or If at the same time insertion or updation is running on it gives you 0 records.

Regards,

Sunil Jain

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 12:11:25 GMT

no, my extraction (qvw reload) is running after cube refreshing on SAP BW side. and we have timeout 30 min between these 2 events

some problems with QV SAP Connector 5.4 SR1

suniljain — Mon, 12 Jul 2010 12:29:37 GMT

is most likely that this is a DataSource that does not send delta data to the BW System via the delta queue but directly via the extractor . You can display the current delta data for these DataSources using TA RSA3 (update mode ='D')

some problems with QV SAP Connector 5.4 SR1

suniljain — Mon, 12 Jul 2010 12:30:23 GMT

It is most likely that a delta initialization had not yet run or that the the delta initialization was not successful. A successful delta initialization (the corresponding request must have QM status 'green' in the BW System) is a prerequisite for the application data to be written to the delta queue.

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 13:22:14 GMT

no, Delta load on SAP BW is finished. Approximately refresh data on SAP BW finish in 8.00 - 8.15 AM, and after this in 8.45 I reload my QVW extract.

so I think may be it's a bug in SAP Connector 5.4 SR1...

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 13:25:13 GMT

Do you use such version of SAP Connector (5.4 SR1) ?

my version of QV Server is 8.50.6299.0409.10 and

SAP Connector: 5.4 SR1 (build 8342)

some problems with QV SAP Connector 5.4 SR1

suniljain — Mon, 12 Jul 2010 13:48:53 GMT

pls try in qlikview

9.00.7320.0409 version. It will solve your poblem.

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 12 Jul 2010 13:54:19 GMT

it's not so simple 🙂 and I don't sure that it solve that problem. because I didn't found any information about inconsistency SAP Caonnector 5.4 and QlikView 8.5.

some problems with QV SAP Connector 5.4 SR1

sparur — Tue, 13 Jul 2010 08:39:43 GMT

I found some interesting things in TRACE log.

1) Trace log for situation when reload successfully and getting data from BW:

Trace.TIMESTAMP Trace.TASKTYPE Trace.TRACE
20100713055846 O Incoming OPEN_STREAM started. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 O SQL syntax check OK. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 O Output-Table: DATA512 . Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 O Reading Job Scheduled. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 B Reading Job started. SAP job number: 01584500 , SAP job name: /QTQVC/READ_DATA . Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 B SQL syntax check OK. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 B Fetch-Cursor OK. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 B Export to shared buffer OK. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 B Fetch-Cursor found no data. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055846 B Reading Job ended without errors. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713055847 F Import data from Memory OK.
20100713055847 F Reading job has reached EOF.

2) Trace for situation when reload successfully BUT NO getting data from BW:

Trace.TIMESTAMP Trace.TASKTYPE Trace.TRACE
20100713062833 O Incoming OPEN_STREAM started. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062833 O SQL syntax check OK. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062833 O Output-Table: DATA512 . Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062833 O Reading Job Scheduled. Packetsize: 20000 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062833 B Reading Job started. SAP job number: 02283300 , SAP job name: /QTQVC/READ_DATA . Packetsize: 6095 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062833 B SQL syntax check OK. Packetsize: 6095 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062834 B Fetch-Cursor OK. Packetsize: 6095 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062834 B Export to shared buffer OK. Packetsize: 6095 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062834 B Fetch-Cursor found no data. Packetsize: 6095 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062834 B Reading Job ended without errors. Packetsize: 6095 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010
20100713062834 F Reading job has reached EOF.

and I see at least 2 different things:

1) 20100713062833 B Reading Job started. SAP job number: 02283300 , SAP job name: /QTQVC/READ_DATA . Packetsize: 6095 , Timeout: 5 , Conversion Routine: 0 , Buffer Percentage: 010

Why packet size has value = 6095 ? in my connection string I use default value for this parameter (20 000)

2) in second situation (when I don't get data) I don't see a row (in trace log) with Import data from memory...

some problems with QV SAP Connector 5.4 SR1

sparur — Tue, 13 Jul 2010 08:42:52 GMT

So, I think that problem in strange packet size for second situation... And I don't know how we can fix it.

Can anyone help me?

some problems with QV SAP Connector 5.4 SR1

pablolabbe — Fri, 23 Jul 2010 23:15:07 GMT

Go back to previous working version of sap connector. Did you have contacted Qliktech Support or your Partner Support ?

some problems with QV SAP Connector 5.4 SR1

sparur — Mon, 26 Jul 2010 06:31:49 GMT

Hello Pablo.

Of course, We have done a rollback on previous version of SAP Connector. And we contacted with QV support team, but we didn't get an answer, unfortunately it's not so quickly as we want.