PROCESSES parameter
NiltonJan 7 2010 — edited Jan 7 2010Oracle 9i and 10g
All OS Versions
I have observed PROCESSES parameter reaching it's limits quite often. Our DBAs often increase this parameter and then schedule Database bounce so that it can take effect.
This procedure is followed even when enqueue_locks resource limit is reached. That is PROCESSES parameter increased and then database bounced.
Is this the correct way to deal with this issue ? Is it possible this is mainly application problems ( INACTIVE sessions existing for a long time , Or Cursors not being closed ) and nothing to do with Database ? Even Oracle user cannot login to database when it reaches limits but database is running.
How do you guys deal with this issue ?