Why The User Profile's SESSIONS_PER_USER Value is Not Taking Effect
(Doc ID 745752.1)
Last updated on OCTOBER 10, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.5.0 to 11.1.0.7 [Release 8.1.5 to 11.1]Oracle Database Cloud Schema 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
After creating a new user profile with SESSIONS_PER_USER resource value is not UNLIMITED.
Then assigning the profile to a user the database is not taking the user profile SESSIONS_PER_USER resource value into consideration. Consequently unlimited number of concurrent sessions can be created.
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 |