Not Getting the Requested Number of Worker Processes When Database Profile SESSION_PER_USER Limit is Set
(Doc ID 1630039.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.4 [Release 10.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Database profile is used to set SESSION_PER_USER to 6. As a result you cannot have more than 6 sessions. If you try to open 7 sessions you get and ORA-02391 error.
This also causes that an SQL may not get the requested number of parallel processes.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |