Oracle 11g user failure and locking Problems

1. User failure During the last installation of a railway system, the Oracle 11g database was found to have a user expiration date. Check the relevant ORACLE data and check whether there is such a problem. [Cause/trigger factor] It is determined that "password_life_time = 180 days" is set in the default profile of oracle11g by default. [Impact and risk] After the password expires, the Business Process connects to the database abnormally and affects the service usage.
After the database password expires, the connection will fail once the business process restarts. [Solution] perform the following operations: 1. Check which proifle is used by the user, generally default: SQL> select username, profile from dba_users; 2. view the password validity period settings of the specified profile (such as default): SQL> select * From dba_profiles s where S. profile = 'default' and resource_name = 'password _ life_time '; 3. Change the password validity period from the default 180 days to "unlimited": SQL> alter profile default limit password_life_time unlimited; after modification, the database does not need to be restarted and takes effect immediately. 4. After modification, the prompted account must change its password again, for example: $ sqlplus/As sysdbasql> alter user SMSC identified by <original password> ---- No new password oracle11g startup parameter resource_limit, whether set to false or true, the password is valid, therefore, you must modify it in the preceding way. The preceding account name must be changed based on the actual account name.   2. User lock problems
Because "failed_login_attempts = 10 times" is set in the default profile in oracle11g by default, the user will be locked when the number of wrong password entered reaches the set value. [Impact and risk] after the account is locked, the Business Process connects to the database abnormally and affects the service usage. After the database account is locked, the connection fails once the business process is restarted. [Solution] perform the following operations: 1. Check which proifle is used by the user, generally default: SQL> select username, profile from dba_users; 2. view the password validity period settings of the specified profile (such as default): SQL> select * From dba_profiles s where S. profile = 'default' and resource_name = 'failed' _ login_attempts '; 3. Change the number of failed attempts to log on from the default 10 to "unlimited ": SQL> alter profile default limit failed_login_attempts unlimited; 4. After modification, users who have not been prompted with a ORA-28000 warning will no longer receive the same prompt; locked accounts must be unlocked, example: $ sqlplus/As sysdbasql> alter use R SMSC identified by Oracle account unlock; 5. After modification, the default profile should be as follows: SQL> select * From dba_profiles where dba_profiles.profile = 'default '; profile resource_name resource_type limit quota ------------- ---------------------- default failed_login_attempts password unlimiteddefault password_life_time password unlimited after modification does not need to restart the database, will take effect immediately.
If the ORA-28000 the account is locked. error alter User Username account unlock; Note: 1. the ekp system checks related users based on application conditions. 2. if the portal project uses oracle11g, you must check the six data source users!