CDC for Oracle uses the Oracle OCI DirectPathLoad bulk loader API to INSERT
the refreshed rows into the target database. The OCI DirectPathLoad API
avoids staging bulk load files on disk by utilizing in-memory loading.
This behavior can be changed to use a JDBC SQL based INSERT operation
if the customer decides not to use bulk load. Note however that bulk
load is by far the fastest method of loading refresh data into a target
database in most cases.
There are some scenarios where fastload cannot be used
1) setting the system parameter refresh_allow_fast_loader = false
2) refresh end on error flag is disabled (refresh_end_on_error = false)
3) rowids are defined (ie. partial refresh with filtering)
4) truncate (clear) is set to do not delete
5) adaptive apply or live audit mapping
6) table contains LOB datatypes
7) If a table can be partially refreshed.If it is sourced from
multiple tables (data warehousing case), or from an IBM i table
containing multiple members.
We use only liveaudit and surely it doesnt make any sense to have direct load for handful of rows each time. But our DBA is a big fan of direct load and was not convinced that direct load is not possible in case of LIve Audit.