ORACLEuserprofile configuration/management/Maintenance

When I create a USER in the new database today, I need to configure resource restrictions. I haven't been playing ORACLE for a long time, and I have been playing this thing almost. Userprofile includes two parts: 1. resource restrictions,

When I create a USER in the new database today, I need to configure resource restrictions. I haven't been playing ORACLE for a long time, and I have been playing this thing almost. Userprofile includes two parts: 1. resource restrictions,

When I create a USER in the new database today, I need to configure resource restrictions. I haven't been playing ORACLE for a long time, and I have been playing this thing almost.

User profile consists of two parts: 1. resource restrictions, but this is not effective by default. The Hong Kong server must be started (resource_limit is true. 2. User Password restrictions. After this configuration, the next login will take effect. The limits configured through user profile take effect the next time the user logs in, and do not take effect for the current session. There is a DEFAULT profile in the database, which is named DEFAULT. There is no limit on this DEFAULT before 11g, but from 11g, PASSWORD_LIFE_TIME is 180, FAILED_LOGIN_ATTEMPTS is 10 times.

Resource restrictions include the following parts:

The password limit consists of the following parts:

The following is a detailed description.

SESSIONS_PER_USER: specifies the maximum number of concurrent sessions for each user. If the maximum session is reached, the ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit error is reported.

CPU_PER_SESSION: Specifies the total CPU time used by each SESSION, in 1/100 seconds. If it exceeds, the following error ORA-02392 will be reported: exceeded session limit on CPU usage, you are being logged off

CPU_PER_CALL: the CPU time used by each CALL, that is, an SQL CALL (a parse, execute, or fetch), in the unit of 1/100 seconds, if it exceeds the report ORA-02393: exceeded call limit on CPU usage.

CONNECT_TIME: limits the total connection time of a session, in minutes. If the maximum value is exceeded, the ORA-02399: exceeded maximum connect time, you are being logged off

IDLE_TIME: Specify the idle time of a session, in minutes. If the maximum value is exceeded, the ORA-02396: exceeded maximum idle time, please connect again

LOGICAL_READS_PER_SESSION: Limit the number of logical blocks read by each session.

LOGICAL_READS_PER_CALL: limits the number of logical blocks read by an SQL statement. If the maximum value is exceeded, the ORA-02395: exceeded call limit on IO usage is reported.

PRIVATE_SGA: limits the allocation of private space of a session in sga.

COMPOSITE_LIMIT: specify the total resource cost of a session.

FAILED_LOGIN_ATTEMPTS: specifies the number of attempts to log on to the account using the wrong password before the account is locked. The default value is 10.

PASSWORD_LIFE_TIME: specifies the number of days for password survival. The default value is 180 days.

PASSWORD_LOCK_TIME: Number of days when the account is locked due to logon failure. The default value is 1 day.

PASSWORD_GRACE_TIME: the number of days after the password expires that can be used to log on to the database. The default value is 7 days.

PASSWORD_VERIFY_FUNCTION: Specifies the password verification function. If it is null, it indicates no.

PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX: these two parameters must be configured together to take effect. PASSWORD_REUSE_TIME indicates the number of days between reuse of the same password, PASSWORD_REUSE_MAX the minimum number of password modifications required for reuse of the same password (excluding the change to reuse password)

Below is the start test:

Test environment: OS RHEL 5.6 X86_64 DB: 11.2.0.2

1. Create a profile for the Hong Kong server

2. view the profile content

3. Modify/view a user's profile

4. Modify the Resource Value in the profile.

This includes two parts: 1. Change to the user-specified value; 2. Change to the default value of the system.

5. Delete the profile

When a profile is deleted, if the profile has been assigned to a user, we need to add cascade When deleting it, the user's profile is changed to the default profile.

6. Modify parameters to make resource restrictions take effect

The default value of this parameter is false, which is a dynamic parameter.

User profile is relatively simple. It is important to understand the meaning of parameters in the lease of servers in Hong Kong.

The following error message is displayed after the resource limit reaches the maximum value.

This article is from the "seriously lose" blog. Please keep this source