The user smsdb in Oracle cannot log on to LOCKED (TIMED)

The user smsdb in Oracle cannot log on to LOCKED (TIMED)

A user created by smsdb to view the status LOCKED (TIMED)

After unlocking, conn smsdb/password still reports an error and is locked again. It is found that the number of wrong logins reaches the Oracle limit 10 times. As a result, subsequent login operations cannot be performed. The solution is as follows:

Check the status and other information of the user in dba_users.
SQL> select account_status, lock_date, profile from dba_users where username = 'smsdb ';
It was found that the account was LOCKED only yesterday. The account status is "LOCKED (TIMED)", indicating that the number of password errors exceeds the maximum number allowed by the system.
View the current maximum number of times
SELECT resource_name, resource_type, limit FROM dba_profiles WHERE profile = 'default ';
Find
FAILED_LOGIN_ATTEMPTS PASSWORD 10
That is to say, the maximum number of password errors allowed is 10, and the account is automatically locked for more than 10 times. So it is useless to alter unlock. You have to relax the limit first.
Change the restricted parameter FAILED_LOGIN_ATTEMPTS to: unlimited.
SQL> alter profile default limit FAILED_LOGIN_ATTEMPTS unlimited;
Or change to a relatively large number of times: 100000
SQL> alter profile default limit FAILED_LOGIN_ATTEMPTS 100000;
Run the following command:
SQL> alter user test account unlock;
SQL> conn smsdb/smsdb
You can log on normally.