Qlik Community

Qlik Replicate

Discussion board for collaboration on Qlik Replicate.

Announcements
QlikWorld online is next week! REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
varadharaj
Contributor II
Contributor II

Replicate LOB columns in SQL Server Target

Hi Team,

We have configured the replicate as below

SQL server source -->Log stream

Log stream -->SQL Server target

We need to replicate LOB columns in target, we have configured maximum value 102400 KB, it is throwing below error

Not enough memory resources are available to process this command (apr status = 720008)

What is the value we need to give for LOB columns without truncating data as it is throwing error for even 1000 KB.

Please let us know the expected behavior.

 

Note :BCP  for loading tables is disabled

 

varadharaj_0-1592900648955.png

 

Labels (1)
1 Solution

Accepted Solutions
lyka
Support
Support

Hi Varadharaj,

 

Since you are replicating lob columns, please try to decrease the full load commit rate.

 

As documented in our user guide:

 

In some scenarios, tasks configured to replicate tables with multiple LOB

columns may consume a large amount of memory. This is because Replicate allocates

memory by multiplying the Limit LOB size to value by the Commit rate during full

load value, the sum of which, it multiplies by the number of LOB columns being

replicated. So, for example, if LOB size is limited to 5 MB and the default commit rate is

used (10000 events), a task replicating 6 LOB columns will consume 30 GB of memory.

Note that other factors such as the database type and version may also affect memory

consumption.

Should you encounter memory consumption issues and suspect that a combination of

the above factors may be the cause, stop the task and lower the value in the Commit

rate during full load field. Then resume the task. Repeat this process until acceptable

performance/memory levels are reached.

These instructions apply to Change Processing and Full Load tasks.

 

Hope this helps!

 

Thanks,

Lyka

View solution in original post

2 Replies
Madhavi_Konda
Support
Support

Hi Varadharaj,
Please check the available memory/disk on your replicate server machine.
Did you set System memory utilization threshold/Disk space threshold in Resouce Control?

Thanks,
Madhavi

 

lyka
Support
Support

Hi Varadharaj,

 

Since you are replicating lob columns, please try to decrease the full load commit rate.

 

As documented in our user guide:

 

In some scenarios, tasks configured to replicate tables with multiple LOB

columns may consume a large amount of memory. This is because Replicate allocates

memory by multiplying the Limit LOB size to value by the Commit rate during full

load value, the sum of which, it multiplies by the number of LOB columns being

replicated. So, for example, if LOB size is limited to 5 MB and the default commit rate is

used (10000 events), a task replicating 6 LOB columns will consume 30 GB of memory.

Note that other factors such as the database type and version may also affect memory

consumption.

Should you encounter memory consumption issues and suspect that a combination of

the above factors may be the cause, stop the task and lower the value in the Commit

rate during full load field. Then resume the task. Repeat this process until acceptable

performance/memory levels are reached.

These instructions apply to Change Processing and Full Load tasks.

 

Hope this helps!

 

Thanks,

Lyka