I am having a strange issue with my main sequence which was running fine before suddenly started aborting at different points whenever restarted. At some point I get error/warnings like
SEQ_dev_tables..JobControl (@Account_Detail): Job SEQ_Accnt_summary.Account_Detail did not finish OK, status = 'Not running'
SEQ_dev_tables..JobControl (fatal error from @Coordinator): Sequence job (restartable) will abort due to previous unrecoverable errors
If I restart the sequence again it will run the above job which was not running but will abort at some other position.
Its really strange but anyhow I need to implement the suggestion made by Ray to re-compile and run again. I will do that on monday and will let you guys know the result.
Ray, when the job was started next time it was in "Finished (see log)" state therefore I believe it doesn't need to compile.
Although when we compiled the main sequence it ran fine but it happened again for next run. I was searching online and found that it might be because the Auto purging in ON and we did have that ON. Now we will try running it by making Auto purge OFF.
But if anyone can suggest if that is because of Auto purge and what might cause the problem.
The Solution we found is just to restart or compile and restart the sequence until if run fine but that's a temporary fix
As you mentioned, your Job status as "Finished (see log)" , means you have some warning in your job. Sequence might be aborted because of that, since the previous job not finished "OK". Please check this too.
girija wrote:As you mentioned, your Job status as "Finished (see log)" , means you have some warning in your job. Sequence might be aborted because of that, since the previous job not finished "OK". Please check this too.
Those warning are just implicit conversion warnings.