ORA-00020: maximum number of processes exceeded

Document ID : KB000117935
Last Modified Date : 22/10/2018
Show Technical Document Details
Issue:
The maximum  number of processes was exceeded on database :

- In  the  alert_AUTO.log file  we can see
ORA-00020: maximum number of processes (800) exceeded
ORA-20 errors will not be written to the alert log for
the next minute. Please look at trace files to see all
the ORA-20 errors.


- The message below about the application server appears :
CAUAJM_E_10527 Timed out waiting for response from the CA WAAE Application Server: [node-name:9000]
CAUAJM_E_50006 Internal API error.
jil_process_object(): do_cat1 fails

 
Environment:
WORKLOAD AUTOMATION AE, Service Pack: 11.3.6 SP5_CUM1, Operating System: LINUX
Cause:
The maximum number of processes in the machine is exceeded
Resolution:

What is the cause of this ORA-00020 error and how do I fix it?

Answer:  The ORA-00020 is a serious production error because a user cannot connect. 

The ORA-00020 is caused by two things:  

  1. Disconnected processes:  Rogue "zombie" connections  to Oracle that are idle (not working).  To fix this, use the ALTER SYSTEM KILL command.  You may also need to kill session at the OS level with the KILL -9 or the ORAKILL command.  

  2. Too few process buckets:  Oracle limits the number of connected processes with the processes parameter, and you may get the ORA-00020 error as the natural result in growth of system usage. 

To fix this, increase the processes parameter, usually doubling the value to allow for future growth.  

The OERR command shows these details for the ORA-00020 error:

ORA-00020: maximum number of processes (string) exceeded

Cause: All process state objects are in use.  

Action: Increase the value of the PROCESSES initialization parameter

Simply increase your processes parameter and you are all set!