Thanks Mahesh and Senthi and here are my comments.
1> When using the Scheduler in a cluster of Integration Servers, you can ensure that repeating and complex tasks run at the desired times by synchronizing the system clocks of all the servers
- There doesnt seems to be a problem with timings when the scheduled tasks run
2> When you schedule a task to run on all servers in the cluster, the server divides the task into a main or parent task, and a child task for each server in the cluster. Do you see the parent and child tasks on IS administration page?
- Yes when we set scheduled task to run on ‘All servers’ then we do see parent and child task created. However this issue is with regards to the scheduled task that is already on IS and happens to point to only one server even when assigned to ‘All servers’
3> Try suspend and reactivate the scheduler task, then the scheduler task must run on both nodes.
- We did try this option and that didnt help
What is your IS core fix levles? Meanwhile you can raise a case against SAG, I assume there should be some fix for this.
- We are at IS_9.7_Core_Fix1 and looks like this issue is addressed in Core_Fix8. Below is note from SAG incident.
In a clustered environment, Integration Server sometimes
does not create child tasks when a new server is added to
the cluster or when an existing server is restarted.
When a task is scheduled to run on all servers in a
clustered environment, Integration Server creates a parent
task and a child task for each server in the cluster. When a
new server is added to the cluster or when an existing
server in the cluster is restarted, Integration Server
creates a corresponding child task upon server restart.
However, Integration Server sometimes does not create the
child task for the newly added server or for the server that
was restarted. As a result, the complete information for all
servers in the cluster is not available on the Scheduler
However client is not ready to move to Fix8 now. Right now we have been manually deleting and creating scheduled task after server restarts so that it creates parent/child task to run on both nodes when set to ‘All servers’. So any means we can find a workaround for this issue without manually creating each time?