Increasing the Oracle job_queue_processes parameter (to comfortably exceed the number of configured IFS batch queues) doesn't actually result in more IFS background jobs running in parallel — several queues sit with jobs in 'Posted' status while only a handful execute at once. Why?

All FAQ questions / Platform, Aurena, and customization

Answer

job_queue_processes controls the database-level ceiling, but actual parallelism per IFS batch queue is separately capped by how many database processes are configured for that specific queue — visible in the Database Processes window. A queue configured with only one or two database processes will never run more jobs simultaneously than that, no matter how high job_queue_processes is set overall. If a particular queue routinely backs up with posted jobs, increase the number of database processes assigned to that queue specifically, rather than assuming a higher global job_queue_processes value alone will increase its parallelism.

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

← Browse Platform, Aurena, and customization questions