Last updated on DECEMBER 06, 2016
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 10.2.0.3 [Release 9.2 to 10.2]
Information in this document applies to any platform.
***Checked for relevance on 21-Sep-2016***
Maximum number of processes exceeded error is neither being captured to the alert log nor to a trace file thus making it difficult to diagnose certain resource crunch issues.
The processes limit being reached can only be verified by querying v$resource_limit view.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms