Inactive Processes On Database - Maximum Number Of Processes Exceeded
(Doc ID 2385729.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Agile Engineering Data Management - Version 184.108.40.206 to 220.127.116.11 [Release 6.2.0]
Information in this document applies to any platform.
After a certain amount of time, users are no longer able to log into Agile EDM any longer. After checking the Alert log, the number of processes has been exceed. The parameter "PROCESSES" is set to "400" whereby a maximum of 100 concurrent users are logged in at the same time.
The issue is not about Oracle session for database manager but rather inactive sessions which is checked by doing the following:
Also, it was noted that the process number is always "1234" but I believe that is another issue in itself. Needed to monitor the system constantly and take manual steps to cleanup inactive sessions.
The issue has the following business impact:
Due to this issue, the number of processes exceeds the maximum number of processes and users can no longer logon to the system. This forces the administrator to have to regularly monitor the system and manually remove any inactivate sessions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document