Skip to main content
Announcements
Product Release Webinar: Qlik Insider airing December 6! REGISTER TODAY!

Memory Consumption of Qlik Replicate increases unexpectedly

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
narendersarva
Support
Support

Memory Consumption of Qlik Replicate increases unexpectedly

Last Update:

Jun 29, 2023 3:46:24 AM

Updated By:

Sonja_Bauernfeind

Qlik Replicate consumes more memory than expected. This article is meant to give a basic understanding of what best practices we can recommend.

Resolution:

  1. We recommend checking the max LOB column length in the table and adding it to the LOB size in task settings. 

    1. Run the below sample query in the database to get the max lob column length:

      select max(DBMS_LOB.GETLENGTH(I_MESSAGE_TEXT)) from  GLOGOWNER.I_LOG_T MAX(DBMS_LOB.GETLENGTH(I_MESSAGE_TEXT))

    2. In the task settings, go to Metadata and open Target Metadata. Set the Limit LOB size to (KB) based on your above findings. 

      limit lob.png

    3. In addition, we recommend increasing memory based on load and monitor. Resource bottlenecks can lead to eventual task failures or impact reliability. If you need assistance with hardware sizing, our professional services can assist you. 
    4. We also recommend adding primary keys in the source DB if not already present.
Labels (1)
Version history
Last update:
‎2023-06-29 06:46 AM
Updated by: