In a training environment, background jobs stop running across every configured batch queue at once, jobs pile up in Posted status with the most recent Ready job several days old, and toggling queues Inactive/Active, using RMB Init Queue, restarting the whole environment, and deleting the oldest stuck job all have no effect.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Have your Oracle DBA check the database initialization parameter JOB_QUEUE_PROCESSES — if this parameter is set to 0, background jobs across every queue simply won't execute at all, producing exactly this 'everything sits there waiting, nothing executes' symptom regardless of individual queue state, restarts, or manual job manipulation. This specific parameter can get accidentally missed or reset during a version upgrade/migration if it isn't explicitly carried over. Raise it to a value greater than zero, commonly 10 in Dev/Test environments, to restore background job execution across all queues.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions