CREATE PROFILE app_user LIMIT
SESSIONS_PER_USER UNLIMITED
CPU_PER_SESSION UNLIMITED
CPU_PER_CALL 3000
CONNECT_TIME 45
LOGICAL_READS_PER_SESSION DEFAULT
LOGICAL_READS_PER_CALL 1000
PRIVATE_SGA 15K
COMPOSITE_LIMIT 5000000;
If you assign the app_user
profile to a user, the user is subject to the following limits in subsequent sessions:
-
The user can have any number of concurrent sessions.
-
In a single session, the user can consume an unlimited amount of CPU time.
-
A single call made by the user cannot consume more than 30 seconds of CPU time.
-
A single session cannot last for more than 45 minutes.
-
In a single session, the number of data blocks read from memory and disk is subject to the limit specified in the
DEFAULT
profile. -
A single call made by the user cannot read more than 1000 data blocks from memory and disk.
-
A single session cannot allocate more than 15 kilobytes of memory in the SGA.
-
In a single session, the total resource cost cannot exceed 5 million service units. The formula for calculating the total resource cost is specified by the
ALTER
RESOURCE
COST
statement. -
Since the
app_user
profile omits a limit forIDLE_TIME
and for password limits, the user is subject to the limits on these resources specified in theDEFAULT
profile.
Setting Profile Password Limits: Example The following statement creates the app_user2
profile with password limits values set:
CREATE PROFILE app_user2 LIMIT
FAILED_LOGIN_ATTEMPTS 5
PASSWORD_LIFE_TIME 60
PASSWORD_REUSE_TIME 60
PASSWORD_REUSE_MAX 5
PASSWORD_VERIFY_FUNCTION verify_function
PASSWORD_LOCK_TIME 1/24
PASSWORD_GRACE_TIME 10;
This example uses the default Oracle Database password verification function, verify_function
. Please refer to Oracle Database Security Guide for information on using this verification function provided or designing your own verification function.
Limiting Concurrent Sessions: Example This statement defines a new limit of 5 concurrent sessions for the app_user
profile:
ALTER PROFILE app_user LIMIT SESSIONS_PER_USER 5;