Oracle profile meaning, modification, new

The profiles file is a configuration collection of password and resource restrictions, including CPU time, I/O usage, idle time, connection time, number of concurrent sessions, password policy, and so on resource usage profile can control session level or statement invocation level. Oracle's own default is much more unrestricted, and the profile is specified when the user is created.

Oracle's profile can be queried in dba_profiles.

SELECT * from Dba_profiles;

The results are as follows:

where the resource class (Resource_type=kernel) means:

--1.session_per_user:
--Specifies the number of concurrent sessions that limit the user.

--2.cpu_per_session:
--Specifies the CPU time limit for the session, in 1% seconds.

--3.cpu_per_call:
--Specifies the CPU time limit for one invocation (parse, execute, and fetch) in 1% seconds.

--4.connect_time:
--Specifies the total connection time for the session, in minutes.

--5.idle_time:
--Specifies the total time, in minutes, that the session will allow for continuous inactivity, and the session is disconnected.

--6.logical_reads_per_session:
--Specifies the number of blocks of data that a session allows to read, including all blocks of data read from memory and disk.

--7.logical_read_per_call:
--Specifies the maximum number of data blocks that are allowed to be read by the Execute SQL (parse, execute, and fetch) call at one time.

--8.PRIVATE_SGA:
--Specifies the maximum amount of space, in bytes, that a session can allow to allocate in the shared pool (SGA).

--9.composite_limit:
--Specifies the total resource consumption for a session, expressed in service units units.

Where the cipher class (Resource_type=password) means:

--1.failed_login_attempts:
--Specifies the maximum number of times an error password is allowed to attempt to log in before the account is locked out.
--
--2.password_life_time:
--Specify the number of days that the same password is allowed to use.
--
--3.password_reuse_time
--a password that can be reused for a long time
--
--4.password_reuse_max:
--refers to the number of times a password modification must be made before the current password can be reused.
--
--5.password_lock_time:
--Specifies the lockout time of the number of failed attempts to reach payback, in days.
--
--6.password_grace_time:
--Specify the number of days to buffer and the number of days before the login expires. If the database password is not modified in the middle, the expiration is invalidated.
--
--7.password_verify_function:
--This field allows complex PL/SQL password validation scripts to be passed as parameters to the Create
The--profile statement. The Oracle database provides a default script, but you can create your own validation rules or use third-party software validation.
--For the function name, the name of the password validation rule is specified, and specifying NULL means that the password verification feature is not used.

Create a custom profile

CREATE Profile My_profile LIMIT
Sessions_per_user UNLIMITED
Cpu_per_session UNLIMITED
Cpu_per_call 6000
Connect_time
Logical_reads_per_session DEFAULT
Logical_reads_per_call 6000
Composite_limit 6000000
PRIVATE_SGA 66K
Failed_login_attempts 6
Password_life_time
Password_reuse_time
Password_reuse_max 5
Password_lock_time 1/
Password_grace_time ;

Can be queried in Dba_profiles:

SELECT * from dba_profiles where profile = ' my_profile ';

The results are as follows:

Allows users to use a custom profile

Alter user apps profile My_profile;

You can query the user's profile by following

SELECT Du.username, dp.*
From Dba_users du, dba_profiles dp
WHERE du.username = ' APPS '
and dp.profile = Du.profile;

The results are as follows

Modify Profile

Alter profile default limit Password_life_time UNLIMITED;

Results:

Delete and retract the profile that has been granted

Drop profile My_profile CASCADE;

When profile is deleted, the user who originally used the profiles uses the default profiles, such as

Set the effective time of the profile parameter

1, the user owns the profile in the password restrictions immediately effective, unrestricted. From this you can see how much Oracle attaches to user passwords.

2, the user owns the profile of the resource restrictions related to the setting of the Resource_limit parameter, when True, when False (the default value) set any value is invalid.

Oracle profile meaning, modification, new