It is 10:
NAME TYPE VALUE
--------------------------
job_queue_processes integer 10
Main Topics
Browse All TopicsI got the following errors in my alert log file:
Tue Oct 23 11:31:08 2007
Thread 1 advanced to log sequence 1136
Current log# 1 seq# 1136 mem# 0: /opt/ora/oradata/owbprod/r
Tue Oct 23 11:41:42 2007
Process J001 died, see its trace file
Tue Oct 23 11:41:42 2007
kkjcre1p: unable to spawn jobq slave process
Tue Oct 23 11:41:42 2007
Errors in file /opt/ora/admin/owbprod/bdu
And here is the content of the trace file:
# more /opt/ora/admin/owbprod/bdu
/opt/ora/admin/owbprod/bdu
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /opt/ora/product/10.2.0/db
System name: SunOS
Node name: ors2ws
Release: 5.10
Version: Generic_118833-36
Machine: sun4u
Instance name: owbprod
Redo thread mounted by this instance: 1
Oracle process number: 4
Unix process pid: 26396, image: oracle@ors2ws (CJQ0)
*** SERVICE NAME:(SYS$BACKGROUND) 2007-10-23 11:41:42.686
*** SESSION ID:(84.1) 2007-10-23 11:41:42.686
*** 2007-10-23 11:41:42.686
Process J001 is dead (pid=15757, state=3):
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
after starting database there are operating system processes created, which serves jobs.
if jour job_queue_processes is 10, tha processes j001 - j010 are created.
this backround proocesses is used to serve actual jobs, so if you have planned let's say 100 jobs in dba_jobs at the same time, only 10 of them are executed and next are executed only after some job finishes.
if someone kills the process in operating system - this is probably reason when oracle detects that job process "died". i think new process is created to serve jobs after you kill one of job process, but i'm not sure. anyway after restart of database there will by 10 processes for jobs.
Cause
JOB_QUEUE_PROCESSES parameter was set to 10 which is a small value.
JOB_QUEUE_PROCESSES specifies the maximum number of processes that can be created for the
execution of jobs. It specifies the number of job queue processes per instance (J000, ... J999).
That is why a lot of jobs died as in the alert log file when the parameter is set to such a small
value.
.
Solution
Make sure you are using SPFILE and then issue the following :
SQL>alter system set JOB_QUEUE_PROCESSES=500 scope=both;
Make sure that the value of the parameter has changed and then check if the error is still
generated in the alert log.
Business Accounts
Answer for Membership
by: rbrookerPosted on 2007-10-23 at 16:13:05ID: 20135299
check your job_queue_processes parameter and make sure it is a non zero value