Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates

Qlik Replicate processing tables with LOB Columns in transactional apply mode

100% helpful (2/2)
cancel
Showing results for 
Search instead for 
Did you mean: 
Bill_Steinagle
Support
Support

Qlik Replicate processing tables with LOB Columns in transactional apply mode

Last Update:

Jan 24, 2024 9:01:07 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jan 24, 2024 1:39:39 AM

A Qlik Replicate task is running and is continuing to have Target Apply Latency against an Oracle Target. The table is applying the data via transactional apply mode even though the table is set up in Batch Optimized mode.

batch optimize mode.png

Resolution

  1. Disable Unlimited Lob on the Task setting > Metadata > Target Metadata tab:

    disable Unlimited Lob.png

  2. On the table level, verify that no override is set in its Task Settings.
    1. In Designer, double-click the table from the table list. 

      selected tables.png

    2. Click Lob Column Handling 

      table settings overview.png

    3. As with the Task Settings before, verify that Unlimited LOB size is not set on table level and that no other setting overrides the Task Settings as this should not be overridden at the Table Level with Unlimited Lob Support

      table column handling.png

 

 

Cause 

The Unlimited LOB size will process the Table in transactional apply mode as it will not see the Table with a Primary Key. With this being set this is causing Replicate not to recognize the Primary Key / Unique Index on the Table.

Related Content 

LOB handling options

 

Internal Investigation ID(s) 

QB-24483

 

Environment

Qlik Replicate 

Labels (2)
Version history
Last update:
‎2024-01-24 09:01 AM
Updated by: