Skip to main content

Official Support Articles

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
QlikWorld 2023, a live, in-person thrill ride. Save $300 before February 6: REGISTER NOW!

Qlik SAP SQL Connector: TIMEOUT_READ_MEMORY error

cancel
Showing results for 
Search instead for 
Did you mean: 
SankarReddyK
Support
Support

Qlik SAP SQL Connector: TIMEOUT_READ_MEMORY error

An SAP SQL connector job is initiated from Qlik by sending a SQL SELECT statement to a SAP function module. Before starting a background (batch) job in the SAP system, the function module performs various checks and handling of the statement. The batch job queries the database using the SELECT statement. The SELECT statement returns a list of packages, each with a fixed number of rows. The shared memory buffer EIBUF (Export/Import buffer) then stores one package at a time. The batch job then waits for Qlik to make a call and retrieve the buffer's content. When the content is retrieved, the connector clears the previously used memory, and the batch job stores the next package in the buffer. The process is repeated until the last package is fetched by Qlik.

TIMEOUT_READ_MEMORY means that the background extraction job in SAP is working to fill the next data package to send to the connector. The package is not ready to send to the connector yet. TIMEOUT_READ_MEMORY will occur in the log until the package is ready to send.

 

How do you find the Qlik Job log error in the SAP system:

  1. Based on the error timestamp, check the SAP connector log in the following location:

    Qlik Sense: C:\ProgramData\Qlik\Custom Data\QvSAPSqlConnector\Log\<Year>\<Month>

    QlikView: C:\ProgramData\QlikTech\Custom Data\QvSAPSqlConnector\Log

    The following information is necessary to examine the SAP task log file. Job Number is a timestamp like 20221116 10:52:44

    JOBNUMBER: 20221116105244

    BATCHJOBNAME: /QTQVC/READ_DATA

  2. In the SAP system, navigate to SAP transaction SM37 to locate the exact timestamp job log.

    SankarReddyK_0-1668599158368.png

  3. Click the job log detail to view a message such as "Timeout reached while waiting for shared buffer." Or some other message.

    SankarReddyK_1-1668599158537.png

 

Resolution

Contact the SAP basis team to verify the buffer parameters as per the SAP standards.

Buffer Parameters configuration: Export/Import buffer EIBUF

SAP Transaction: ST02.

Check the SAP note 702728 - Profile parameters for export/import buffer instances.

NOTE: When the parameters have been changed, restart the SAP system to activate the new values.

The following parameters are important:

rsdb/obj/buffersize:

Syntax for correct size: PHYS_MEMSIZE * 1024 * 0,01.

For example, if the server has 35 Gb of memory, the correct value should be 358400.

rsdb/obj/max_objects:

Syntax for correct size: rsdb/obj/buffersize / 4.

Correct value based on rsdb/obj/buffersize of 358400 = 89600.

rsdb/obj/large_object_size:

Default: 8192. Because this default value has proven to be too small, it has been changed as follows in kernel patches:

As of kernel Release 7.40 PL 68, 7.41 PL 35, and 7.42 PL 3, the default has been increased to 250000.

The parameter values can be checked in transaction RZ11 or in transaction ST02.

Note: If the issue persists, file a support ticket with the logs discussed for further investigations.

 

Environment:

Qlik SAP Connectors 

Labels (1)
Version history
Last update:
‎2022-11-16 07:59 AM
Updated by: