Question: I have jobs that fail to run, and I
wonder if my setting for job_queue_processes is too low?
How can I tell when my job_queue_processes parameter is
optimized?
Answer: The job_queue_processes
is the number of concurrent jobs running, which your DBA should know
from their daily job stream. The easy way to set
job_queue_processes is to set it to a reasonable value such as
five, since only very busy batch system will have n=more than five
concurrently executing batch jobs.
If job_queue_processes is too low, jobs may be seen
waiting in the execution queue for a process to become free. You
can also monitor the job queue and set job_queue_processes
to the high water mark of executing jobs. You can write a monitor
to track the maximum count from dba_jobs_running to find
the optimal value for job_queue_processes.
The book "Oracle
Job Scheduling" addresses the optimization of
job_queue_processes in detail.
 |
|
Get the Complete
Oracle SQL Tuning Information
The landmark book
"Advanced Oracle
SQL Tuning The Definitive Reference" is
filled with valuable information on Oracle SQL Tuning.
This book includes scripts and tools to hypercharge Oracle 11g
performance and you can
buy it
for 30% off directly from the publisher.
|
