are oracle clobs not recognised by qlik?

[KG_Maleka]

When selecting a table on the task, All columns but clobs gets listed. we unticked lob limiter but tis does not change the listing. What must we do.

[Lucas_Gatling]

Here is an exerpt from our Online help for using a CLOB types for Oracle source

CLOB

To use this data type with Qlik Replicate, you must enable the use of CLOBs for a specific task.

During CDC or during Full Load when the Allow unlimited LOB size option is enabled, LOB data types are supported only in tables with a primary key or unique index.

https://help.qlik.com/en-US/replicate/May2022/Content/Replicate/Main/Oracle/ora_source_data_types.ht...

[john_wang]

Hello @KG_Maleka ,

Qlik Replicate supports LOBs replication, and the LOB columns are recognized automatically. For Full Load ONLY task, nothing special; for CDC (or Full Load + CDC) task,  it requires the table has a primary key or unique index, @Lucas_Gatling mentioned that as well. This is for Run time stage.

When it comes to task Design stage, the LOB columns can be recognized and being listed in the task Design or table setting windows, even NO PK nor Unique Index available for a table, or even "Replicate LOB columns" option is turned off in task setting. Below is an example of table setting (column "notes" is a CLOB):

Maybe you can paste a sample of your table creation DDL we'd love to confirm the behavior for you. BTW, let us know your Replicate version, Oracle client/server version, these information help us to understand the issue.

Regards,

John.

[KG_Maleka]

NB: note and template columns are not reflected, see the pic below

[john_wang]

Hello @KG_Maleka ,

Thanks for your update however it's hard to tell the reason by the pictures this time. May we know your Replicate version, Oracle client/server version?

The table works fine for me in my labs: Replicate 2022.5 + Oracle 19c client + Oracle 12c server

Or you may try to troubleshoot the issue by:

1- Connect to Oracle by SQLPlus , using the as same credential as Replicate endpoint

2- Run below SQL to see if you can get the 2 CLOB columns

select * from rcm.acm_audits where 1=0;

(where 1=0 means getting the table's metadata only)

Hope this helps.

Regards,

John.

[Heinvandenheuvel]

Maybe, just maybe this was a timing issue during the design. Now that lobs are enabled, save it the task,  drop the table and re-add it to the task. LOB columns still not there?

Just a WAG

Good luck, Hein.