Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Solving the Informatica Dilemma: On-Demand Briefing - Watch On Demand!
cancel
Showing results for 
Search instead for 
Did you mean: 
haiderpasha
Contributor III
Contributor III

High Latency observed for Oracle Taget for one task

We have May 2025 (2025.5.0.134) configured, and we've started noticing that one specific task—reading data from AS400 DB2 iSeries and writing to Oracle—is taking significantly longer to complete replication.

This issue appears to be isolated to that single task, as other tasks with similar configurations run without problems. There are no errors reported in the logs except the warnings.

 

haiderpasha_0-1750239858564.png

 

Labels (3)
1 Solution

Accepted Solutions
Dana_Baldwin
Support
Support

Hi @haiderpasha 

The warnings indicate that no data would have been changed on the target if the change had been applied.

Can you provide the actual task log?

Are changes being applied in one-by-one mode (search the log for 'one-by')?

As the warning suggests - have you checked the attrep_apply_exceptions table on the target to see if there are additional details to help with the root cause?

Please confirm that the tables with these warnings match between source and target as far as metadata is concerned.

Is the task configured to use batch apply? If so, are there foreign key constraints on the target tables? If FK are used, the apply method should be transactional apply, not batch apply.

If there are no errors or one-by-one mode, the performance tuning / configuration help is handled by our Professional Services team. You can contact your Account Manager to purchase hours and schedule help.

Thanks,

Dana

View solution in original post

1 Reply
Dana_Baldwin
Support
Support

Hi @haiderpasha 

The warnings indicate that no data would have been changed on the target if the change had been applied.

Can you provide the actual task log?

Are changes being applied in one-by-one mode (search the log for 'one-by')?

As the warning suggests - have you checked the attrep_apply_exceptions table on the target to see if there are additional details to help with the root cause?

Please confirm that the tables with these warnings match between source and target as far as metadata is concerned.

Is the task configured to use batch apply? If so, are there foreign key constraints on the target tables? If FK are used, the apply method should be transactional apply, not batch apply.

If there are no errors or one-by-one mode, the performance tuning / configuration help is handled by our Professional Services team. You can contact your Account Manager to purchase hours and schedule help.

Thanks,

Dana