Hi Charuka.  Are there other jobs in the same queue that are still in the executing status holding these jobs from executing?  Have you tried to right mouse click and select execute?  If no other jobs are executing and you can’t get your job to execute, you may need to create a case to IFS so that this can be investigated for you.  Please advise if you have any questions.  Thanks!  Jane

Charuka,

There are several factors to consider with this kind of a situation.  Some of these could be:

1. prior runs of the background job(s) affected - did any fail with errors?
2. database locks - are there any preventing this job from starting?
3. problems with the batch queue where the background job is scheduled - is the queue itself inactive or somehow prevented from initiating new jobs?
4. batch queue planning and job scheduling - are there excessive numbers of jobs being triggered at the same time - or does a resource intensive job hold up other quicker jobs from running?  If yes to either situation, could some jobs be moved to a different queue to avoid scheduling bottlenecks?
5. process count for the batch queue - are there sufficient JOB_QUEUE_PROCESSES to accommodate this job and those of the other batch queues within the Oracle database?

There may also be other issues occurring in the Oracle database which could hinder or altogether block background jobs from starting.  Troubleshooting this kind of an issue can take time.

Eugene Wager, Systems Engineer --- IFS Support