Kkjcre1p: unable to spawn jobq slave process error Solution

The customer reported that the workstation software could not connect to the backend occasionally and could be connected for a period of time. It was initially suspected that the number of connections was insufficient. The following are some of the errors in the log.
 
First log
Mon Sep 26 15:06:59 2011
Process m000 died, see its trace file
Mon Sep 26 15:06:59 2011
Ksvcreate: Process (m000) creation failed
Mon Sep 26 15:08:06 2011
Process m001 died, see its trace file
Mon Sep 26 15:08:06 2011
Ksvcreate: Process (m001) creation failed
Mon Sep 26 15:11:26 2011
Process J000 died, see its trace file
Mon Sep 26 15:11:26 2011
Kkjcre1p: unable to spawn jobq slave process
Mon Sep 26 15:11:26 2011
Errors in file/home/oracle/orabase/admin/ORACLE/bdump/oracle_cjq0_28852.trc:
Second log
ORA-00444: background process "EMN0" failed while starting
ORA-00020: maximum number of processes () exceeded
Mon Sep 26 15:16:08 2011
Process J000 died, see its trace file
Mon Sep 26 15:16:08 2011
Kkjcre1p: unable to spawn jobq slave process
Mon Sep 26 15:16:08 2011
Errors in file/home/oracle/orabase/admin/ORACLE/bdump/oracle_cjq0_28852.trc:
According to the prompts, we can see that the system cannot generate job-related processes, and an error occurs when the maximum processes limit is reached.
View system processes and sessions
SQL> show parameter processes
 
NAME TYPE VALUE
-----------------------------------------------------------------------------
Aq_tm_processes integer 0
Db_writer_processes integer 1
Gcs_server_processes integer 0
Job_queue_processes integer 10
Log_archive_max_processes integer 2
Processes integer 150
SQL> show parameter sessions
 
NAME TYPE VALUE
-----------------------------------------------------------------------------
Java_max_sessionspace_size integer 0
Java_soft_sessionspace_limit integer 0
License_max_sessions integer 0
License_sessions_warning integer 0
Logmnr_max_persistent_sessions integer 1
Sessions integer 170
Shared_server_sessions integer
SQL>
View the processes of the current system
SQL> select count (*) from v $ process;
 
COUNT (*)
----------
148
 
SQL>
The error message is displayed because the number of processes is insufficient. Change the number of processes connections to 300. The database restart problem does not occur again.
 
Note:
 
1: kkjcre1p: unable to spawn jobq slave process has several possible causes:
 
1. The job_queue_processes parameter is set to an excessively small value.
2. The number of sessions and the number of connections set by the parameter session and processes cannot meet the service requirements.
3. The pga_aggregate_target parameter is exhausted.
4. OS resources are exhausted.
 
In this case, an error is reported because the maximum number of processors has reached the maximum limit.
 
2:
Oracle background processes include ora_j000_ORACLE and ora_j0001_ORACLE. These processes are all slave processes generated by the background process cjq0 (Coordinating program job Queue background processes). These ora_j000 are job processes, the maximum number is controlled by the initialization parameter job_queue_processes.
 
 
Author "taste life with heart !"