Job getting triggered twice with same Job_Run_Id

Discussion created by SandeepJ on Feb 7, 2014
Latest reply on Feb 7, 2014 by SandeepJ

Hello All,

Problem :

We are observing no jobs running in clarity on a server(for eg: Server01) after completion of particular job (job1), but the same job is processing fine on the other servers(Server02, Server03).

No jobs gets triggered on Server01, untill we restart BG services of that server. Even after restarting the BG services, the same job (job1) gets triggered with the same Job_Run_Id.

This issue mostly happens with Jobs having multiple runs.