The underlying cause of the resource spike was the execution of this query using aggressiveOracle PARALLEL hints, which exhausted available target DB CPU/memory resources.
Resolution
To prevent future resource contention and CPU/memory alerts in the target database, parallelism hints must be disabled or tuned within Qlik Replicate. This involves modifying two internal parameters across the Full Load and CDC stages: bulkUseParallel and directPathParallelLoad.
bulkUseParallel is for CDC / Change Processing and is enabled by default (true). It instructs Qlik Replicate to inject the Oracle PARALLEL hint into bulk DML statements for better target performance.
Setting it to false stops queries such as UPDATE /*+ PARALLEL(tempview) */ ... from executing in parallel, preventing CPU spikes.
This may cause a slight performance degradation during high-volume CDC processing.
directPathParallelLoad is for Full Load and enabled by default (true). It enables Direct Path loading using parallel processing only during the initial Full Load phase. It has no impact on the daily CDC.
Setting it tofalseproactively protects the DB during table reloads.
Will likely increase the time required to complete Full Load operations.
How to set the Internal Parameters in Qlik Replicate:
Navigate toManage Endpoint Connection→Targetsand select your Endpoint