Property | Description |
Parameter type | Integer |
Default value |
|
Modifiable |
|
Range of values | 0 to number of session licenses |
Basic | No |
Real Application Clusters | Multiple instances can have different values, but the total for all instances mounting a database should be less than or equal to the total number of sessions licensed for that database. |
LICENSE_MAX_SESSIONS
specifies the maximum number of concurrent user sessions allowed. When this limit is reached, only users with the RESTRICTED SESSION
privilege can connect to the database. Users who are not able to connect receive a warning message indicating that the system has reached maximum capacity.
A zero value indicates that concurrent usage (session) licensing is not enforced. If you set this parameter to a nonzero number, you might also want to set LICENSE_SESSIONS_WARNING
(see "LICENSE_SESSIONS_WARNING").
Do not enable both concurrent usage licensing and user licensing. Set either LICENSE_MAX_SESSIONS
or LICENSE_MAX_USERS
to zero.
Note:
1. Related: V$LICENSE, parameter LICENSE_SESSIONS_WARNING and LICENSE_MAX_USERS.
Users received ORA-19 if they are not allowed to connect.
Eg: ORA-19 "maximum number of session licenses exceeded"
Messages are written to the alert log for each connect attempt made once LICENSE_MAX_SESSIONS is reached.
Eg: If the user has RESTRICTED SESSION privilege:
"License maximum (10) exceeded, DBA logon allowed"
If the user was refused from connecting:
"Non-DBA logon denied; current logons equal maximum (10)"
2. Query for the current value of the parameter
select name, value, isdefault, isses_modifiable, issys_modifiable,
isinstance_modifiable, isdeprecated, description
from v$parameter
where upper(name) = ‘LICENSE_MAX_SESSIONS’;
NAME | VALUE | IS DEFAULT | ISSES_ MODIFIABLE | ISSYS_ MODIFIABLE | ISINSTANCE_ MODIFIABLE | IS DEPRECATED | DESCRIPTION |
license_max_sessions | 0 | TRUE | FALSE | IMMEDIATE | TRUE | FALSE | maximum number of non-system user sessions allowed |
No comments:
Post a Comment