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

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
Husseyn
Contributor
Contributor

Task not Applying Incoming Changes

I have set up tasks reading from a logstream staging task however  i have noticed two tasks have incoming changes that are not being released. These  are stuck on Applying changes on Disk and others are in memory but they're not being released to allow new changes.

I have another task that's updating normally and it's also reading from the same logstream task. What could be the issue with the other two.

The logstream task picking from source to logstream target is working fine.

source Endpoint point is Oracle and Target is SQL server

2 Replies
boatswainshy
Contributor
Contributor

Hi team,

Thanks for writing!
I notice your queries are unanswered. I hope you've already fixed it. If not, please confirm the following.

  1. Did you restart the Qlik Enterprise Manager service after updating the Log On As user credentials?
  2. Are you using a Fully Qualified Domain Name in the Server Connection properties?
  3. Have you added the new user account in Qlik Replicate in addition to the Qlik Enterprise Manager?

https://community.qlik.com/Task-not-Applying-Incoming-Changes/td-p/1696709-penalty kick online

Thank you!

Kind regards,

boatswainshy

Heinvandenheuvel
Specialist III
Specialist III

>> These  are stuck on Applying changes on Disk and others

So really the problem is more 'Task not Applying Outgoing Changes' 🙂

Do you have connectivity to the target

  • Use 'test' on the target end-point in the UI
  • Check for (intermediate) flashing red marks on the target endpoint in the task monitor screen
  • Anything recent under 'Messages'  in the task monitor UI?

Did you check the (tail) reptask-log for errors or warnings?

Increase the logging level for TARGET_APPLY to TRACE or even VERBOSE to see what it it trying

Finally, check the target DB with SP_WHO2 or similar for active connections/active SQL for the PID of the Task from the Replicate server. It is a reasonable query, is it blocked? 

Hein.