Why The User Profile's SESSIONS_PER_USER Value is Not Taking Effect
(Doc ID 745752.1)
Last updated on DECEMBER 23, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 8.1.5 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata 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.
***Checked for relevance on 20-SEP-2012***
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.
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