Why The User Profile's SESSIONS_PER_USER Value is Not Taking Effect
Last updated on NOVEMBER 22, 2016
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 8.1.5 to 11.1]
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms