topic Re: Regarding Oracle SQL*Loader's Direct-Path INSERT. in Qlik Replicate

Regarding Oracle SQL*Loader's Direct-Path INSERT.

iti-attunity-sup — Wed, 17 Jun 2026 04:34:57 GMT

Hello Support Team,

I hope you are doing well.

I would like to clarify the recommended settings when the source database uses Oracle SQL*Loader's Direct-Path INSERT.

My understanding is that because Oracle SQL*Loader's Direct-Path INSERT writes blocks directly to the disk without going through the buffer cache,
it does not generate REDO logs or archive log files.
Therefore, if we want to ensure REDO logs are generated, we need to either enable the table's LOGGING setting or switch to FORCE LOGGING mode.

Based on this, I assumed that Qlik Replicate would not be able to perform CDC on data inserted into the source DB via Oracle SQL*Loader's Direct-Path INSERT.
However, upon reviewing the limitations, I could not find any specific limitations or recommendations regarding Direct-Path INSERT.

Are there any recommended settings on the source Oracle database side when using Oracle SQL*Loader's Direct-Path INSERT?

Best regards.

Re: Regarding Oracle SQL*Loader's Direct-Path INSERT.

iti-attunity-sup — Wed, 17 Jun 2026 05:48:04 GMT

Hello Support Team,

Based on our internal verification, data was successfully synchronized when the table's LOGGING setting was set to YES.
However, when the table's LOGGING setting was set to NO, the data could not be synchronized.

Aside from verifying whether the table's LOGGING setting is set to YES,
are there any other potential impacts on CDC or points of caution (such as limitations or concerns) that we should be aware of when using Oracle SQL*Loader's Direct-Path INSERT?

Best Regards.

Re: Regarding Oracle SQL*Loader's Direct-Path INSERT.

DesmondWOO — Thu, 18 Jun 2026 04:26:32 GMT

Hi @iti-attunity-sup ,

In short, as long as those changes are captured in the redo log, Qlik Replicate can read them. Therefore, the core requirement lies on the Oracle side rather than Qlik Replicate.

When the customer performs a direct-path insert, a huge volume of changes is generated in the redo log. This will impose a heavy load on both the Oracle DB and Qlik Replicate, which will temporarily cause high source latency.

Regards,
Desmond