Full Load Commit Interval Not Taking Effect – Oracle Target Only Receives Data After Entire Table is Loaded

[EY_C]

Hi Support,

We are experiencing an issue with the Full Load Tuning - Commit rate during full load setting in Qlik Replicate.

Environment Details:

• Source: DB2 AS400

• Target: Oracle

We have set the Full Load Commit Interval to a specific number (e.g., 1000 rows), expecting that Replicate will commit data to the Oracle target in chunks as rows are loaded.

However, in our observation, data is only committed to the Oracle target after the entire table has been fully loaded. This behavior defeats the purpose of incremental commits and affects large tables significantly in terms of visibility and transaction size.

We would like to confirm:

1. Is this a known issue or limitation specific to the Oracle target or to DB2 AS400 as a source?

2. Are there any additional settings or task options required to enable chunk-wise commits during full load?

3. How can we verify if the Full Load Commit Interval is actually being applied at runtime?

Please advise how we can resolve or further diagnose this.

[Dana_Baldwin · Accepted solution]

Hi @EY_C 

Please check if the Oracle target endpoint, advanced tab, has the option "Use direct path full load" enabled. I suspect this may cause this type of behavior as data blocks are written directly to the database files, avoiding the overhead of the database.

"Use direct path full load: Select this to use the OCI direct path protocol for bulk loading Oracle tables. This is the default selection."

Setting advanced connection properties | Qlik Replicate Help

Thanks,

Dana