Monitoring the Oracle Database - "Processes" Initialization Parameter

If you want to find out whether your Processes initialization parameter value is sufficient enough so that there won't be any issues for the users to connect to the database

Follow the Process below to monitor the processes initialization parameter

1. Connect to the database as sys user

SQL> conn / as sysdba

SQL> select * from v$resource_limit where resource_name in ('processes','sessions');

RESOURCE_NAME CURRENT_UTILIZATION MAX_UTILIZATION
------------------------------ ------------------- ---------------
INITIAL_ALLOCATION LIMIT_VALUE
------------------------------ ------------------------------
processes 207 210
350 350

sessions 213 218
700 700



In The above output the Max_utilization is 210 and limit_value is 350. So the Maximum utilization is 210 < 350. So the Parameter is good Enough.

Consider increasing the Processes parameter if max_utilization reaches 350 value.
Note: Sessions parameter is automatically adjected as per the Processes setting.

You can also check whether there were any connection refusesals when the processes parameter has reached its limit using the following

lsnrctl services

The output of the above command is

Instance "R12VIS", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "R12VIS", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:2187 refused:0 state:ready

The state should be ready aad refused should be 0. If there is any value against refused, and state is blocked then the listener is not accepting any connections because database has reached its processes max_limit.