topic SAP EXPORT_BUFFER_NO_MEMORY error in QlikView

SAP EXPORT_BUFFER_NO_MEMORY error

Mon, 26 Jan 2026 21:26:37 GMT

Some Qlikview extracts are abending on the SAP side with the message "EXPORT_BUFFER_NO_MEMORY".
The error points to the parameter "rsdb/obj/buffersize".

In Qlikview the error appears as :

Custom read failed
SQL SELECT *
FROM KNA1

Running RSPFLDOC via SE38 shows the parameter values:

Appl.area: General system
Parameter Type: Integer Value
Changes allowed: Change permitted
Valid for oper.system: All
Minimum: 16
Maximum: 256,000
DynamicallySwitchable: (blank)
Same on all servers: (blank)
Dflt value: 4096
Profile value: 20000
Current value: 20000

Has anyone else encountered this error?
How do others have "rsdb/obj/buffersize" configured?
Thanks,
Ben

SAP EXPORT_BUFFER_NO_MEMORY error

disqr_rm — Tue, 16 Feb 2010 19:25:36 GMT

Your buffersize seems to be very low, but it all depends on how much data you are exporting. How many record you have in KNA1?

I got following buffer size in my system, but this could vary in many ways and depends on many other profile parameters. You should check with your basis guys what can be adjusted with exisitng hardware (available memory, etc.).

Dflt value 4096
ProfileVal 400000
Current value 400000

Hope this helps.

SAP EXPORT_BUFFER_NO_MEMORY error

Tue, 16 Feb 2010 19:45:45 GMT

Thanks for the quick response. KNA1 has 90,000 records.

SAP EXPORT_BUFFER_NO_MEMORY error

disqr_rm — Tue, 16 Feb 2010 20:05:13 GMT

It's not too much. Ask your basis guys to analyze the ABAP dump and adjust buffer parameters. You may also want to play with SAP Connector settings (buffer, packet sizes, etc.) it's all documented well in SAP Connector installation guide.

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Wed, 19 May 2010 19:34:45 GMT

Rakesh,

Hi. We just upgraded to 9.0 SR4 / SAPConnector Version 5.4. We were on 9.0 SR3 / SAPConnector 5.3 in our development environment and things were working fine. Well a new release of connector came out and we upgraded. Now we are getting the following:

SQL Select *
5/19/2010 13:34:32.1026415 Information 05/19/10 13:34:31: 1472 FROM KNVV
5/19/2010 13:34:32.1026415 Information 05/19/10 13:34:31: 12 fields found: %KNVV, Ship To, %SalesOffice_Key, Customer Emp NonEmp, Customer Acct Assignment Grp, Customer Payment Terms, Customer Invoice Periods, Customer Grp1, Customer Grp2, Customer Grp3, Customer Acquisition,
5/19/2010 13:42:43.3717842 Information Customer Grp5, 1,759,503 lines fetched
5/19/2010 13:42:46.6534752 Information 05/19/10 13:42:43: 1475 store KNVV into qvd\KNVV_SalesOrg.qvd
5/19/2010 13:42:46.8722546 Information 05/19/10 13:42:46: 1478 drop table KNVV
5/19/2010 13:42:46.8722546 Information 05/19/10 13:42:46: 1485 [ADRC]:
5/19/2010 13:42:46.9035088 Information 05/19/10 13:42:46: 1486 Load
5/19/2010 13:42:46.9035088 Information 05/19/10 13:42:46: 1487
5/19/2010 13:42:46.9035088 Information 05/19/10 13:42:46: 1488 [ADDRNUMBER] as [Customer AddrKey],
5/19/2010 13:42:46.9191359 Information 05/19/10 13:42:46: 1489 [HOUSE_NUM1] as [Customer House Number],
5/19/2010 13:42:46.9191359 Information 05/19/10 13:42:46: 1490 [STREET] as [Customer Street],
5/19/2010 13:42:46.9191359 Information 05/19/10 13:42:46: 1491 [SORT1] as [Customer Search Term 1],
5/19/2010 13:42:46.9347630 Information 05/19/10 13:42:46: 1492 [SORT2] as [Customer Search Term 2]
5/19/2010 13:42:47.2629321 Information 05/19/10 13:42:46: 1494 SQL SELECT *
5/19/2010 13:42:47.2629321 Information 05/19/10 13:42:46: 1495 FROM ADRC
5/19/2010 13:42:47.2629321 Information 05/19/10 13:42:47: 5 fields found: Customer AddrKey, Customer House Number, Customer Street, Customer Search Term 1,
5/19/2010 13:51:26.3483128 Information Customer Search Term 2, Error: Custom read failed
5/19/2010 13:51:26.5670922 Information 05/19/10 13:51:26: General Script Error
5/19/2010 13:51:26.5670922 Information 05/19/10 13:51:26: Execution Failed
5/19/2010 13:51:26.5670922 Information 05/19/10 13:51:26: Execution finished.

We have checked all authorizations in SAP, did a trace in SAP and everything is fine. Any ideas?

I checked our buffer sizes and they are 4096, 55000, 55000. We are trying to process 1.8 million rows of data.

Thanks

Thom

SAP EXPORT_BUFFER_NO_MEMORY error

disqr_rm — Thu, 20 May 2010 18:20:46 GMT

Hi Thom,

Looking into error log you posted, it seems there is a problem with your script and nothing with SAP. Possible that you could post your QVW here?

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Thu, 20 May 2010 18:40:57 GMT

Thanks Rakesh. I am out of the office sick today, but I will post it tomorrow. We upgraded our DEV environment to 9.0 SR3 with SAPConnector 5.3 and everything ran fine. We then upgraded one more time to 9.0 SR4 with SAPConnector 5.4. I made no changes to my QVW. Is there something different in 5.4 vs. 5.3 of the SAPConnector?

Thanks
Thom

SAP EXPORT_BUFFER_NO_MEMORY error

disqr_rm — Thu, 20 May 2010 19:00:14 GMT

Nope, nothing I noticed. As long as you have imported the new transport requests, and correct versions of them based on your R/3 version, it should work just fine. Do post your QVW and I can run it through my env to see if it works for me or not.

Get well soon.

Rakesh

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Mon, 24 May 2010 15:26:44 GMT

Rakesh,

Maybe you can explain this to me. Most of my select statements are select *, they all work except for one (ADRC) table in SAP. I listed the fields I am selecting and it works fine. Here is one that I listed the fields I am selecting and it aborts.

Custom read failed
SQL Select ZORDER ZACTIVITY ZSTATUS ZWDATE ZHOURS
from ZTRPST where ZWDATE >= '20100103' and ZEMPEQP = 'P'
and ZORDER between '000040000000' and '000049999999'

Thanks

Thom

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Thu, 27 May 2010 16:22:50 GMT

We upgrade to 9.0 SR4 and SAP Connector 5.4 SR1. We are now getting the following error on the SAP side. Any ideas?

Timeout reached while waiting for clear memory

SAP EXPORT_BUFFER_NO_MEMORY error

Thu, 27 May 2010 16:34:05 GMT

I tried upgrading to 5.4 but performance was much worse with our 4.6c system.
In the release notes it mentioned that 5.4 would only for 6.0 and above.

Also, I've had several problems with "Select * " on large ( wide ) tables. It works much better when fields are explicitly listed.

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Wed, 09 Jun 2010 12:59:06 GMT

After working a few days with QlikView Tech Services, and numerous modifications to our connect string we have come to the conclusion the problem is in the Packetsize=n (20K) default value. We tried adjusting it from 20k down to 5K and got the 5K to run with no problems in (9.0 SR4 / SAPConnector 5.4 SR1). Do not use the default value, you will have to enter the Packetsize=5000K in your connect statement manually. They have logged it as bug ID 29004 with their QA department. If approved the bug will hopefully be fixed in the next Service Release - however due to uncertainties regarding potential related problems and program priorities they cannot guarantee a fix date at this time.

They will keep me updated on any new developments in this regard.

Original Case Description:

Customer is experiencing timeouts when reloading from SAP after upgrade to v9 SR4. The logfiles and the SAP document for additional information is attached to the case.

SAP EXPORT_BUFFER_NO_MEMORY error

Lars_Wahlstedt — Wed, 09 Jun 2010 13:56:11 GMT

The reasons you got timeouts on the SAP side was several APPLYMAP statements in the preceding load statement that needed too much time. Our suggestion was to move the applymap statements to a Load ... Resident statement after the SELECT statement.

By doing this you can keep the Packetsize at 20000 and get much better speed for the download.

In a future release we will increase the Timeout limit for the SAP side and include a recommendation that extensive manipulation in the LOAD statement should be done in a LOAD.... Resident statement after the SELECT. The Packetsize default value will not be changed.

Kind Regards,

Lars Wahlstedt

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Wed, 09 Jun 2010 14:02:45 GMT

Lars,

Why would it work fine in our Production environment running 8.5 / 5.3 connector? Is it a memory issue on the SAP side or QlikView side? My production environment has 132Gig, where my development environment has 16Gig on a virtual box. Thanks Thom

SAP EXPORT_BUFFER_NO_MEMORY error

Lars_Wahlstedt — Wed, 09 Jun 2010 14:12:50 GMT

we reduced the SAP side timeout from 60 sec to 30 sec in 5.4, your APPLYMAP needed 55 sec. So you have been lucky in 5.3 🙂

/ Lars W

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Wed, 09 Jun 2010 14:18:13 GMT

Lars,

Is there a parameter on the connect string that I can modify the SAP timeout to take advantage of the 20K? Or is that controlled through the transports

Thanks

Thom

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Tue, 03 Aug 2010 12:43:49 GMT

Lars,

Am I able to modify the timeout parameter in the connect string? I am trying to extract financial data from GLPCA. When I cut down the number of rows extracted it works, but the user has sent me their requirements and I had to increase the number of rows to extract. Now the job aborts. What are the work-arounds? The job is aborting on the SAP side with the following message:

Date Time Message text Message class Message no. Message type

08/02/2010 13:40:23 Job started 00 516 S
08/02/2010 13:40:23 Step 001 started (program /QTQVC/READ_DATA, variant &0000000001216, user ID QLIKVIEW) 00 550 S
08/02/2010 18:58:50 Timeout reached while waiting for clear memory. 00 001 E
08/02/2010 18:58:50 Job cancelled after system exception ERROR_MESSAGE 00 564 A

SAP EXPORT_BUFFER_NO_MEMORY error

Lars_Wahlstedt — Tue, 03 Aug 2010 13:41:56 GMT

Hi Thom,

you are not able to modify this specific timeout. Make sure you do no manipulations in the Load statement in the QV script, just store the data directly to a QVD-file. The reason you get timeouts is that QV fetches data from SAP too slowly.

Regards, Lars

SAP EXPORT_BUFFER_NO_MEMORY error

tmumaw — Tue, 03 Aug 2010 14:49:27 GMT

I am trying to extract from SAP our GLPCA table. When I extract just a few rows for years 2005 - 2010 it runs fine, but when I extract all the rows the user has requested it aborts. I am trying to run one year at a time and merge the files in Qlikview. Years 2005 - 2009 will never change, so it will be a one time extract. Thanks for your help. I will let you know the out come

Thom

SAP EXPORT_BUFFER_NO_MEMORY error

suniljain — Tue, 03 Aug 2010 16:40:20 GMT

The main reason for time out is when qlikview connector donot get any response from SAP R/3 within specific time. because there are lots of activity running on production server on database . so some time server engage in doing that activity and unable to give response to connector request. this types of issue normaly happen in SAP R/3 environment.

Sometime low cache memory is also responsible for time out reason.

Regards

Sunil Jain.