Shulou(Shulou.com)06/01 Report--

Create a user smsdb to view the status LOCKED (TIMED)

After unlocking, conn smsdb/password still reported an error, and then was locked; finally, it was found that the number of wrong logins reached the oracle limit of 10 times; resulting in subsequent unable to log in operation. The solutions found online are as follows:

Check the user's status and other information 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, and the account status was "LOCKED (TIMED)". The number of password errors exceeded the maximum number allowed by the system setting.

View the maximum number of times now set

SELECT resource_name,resource_type,limit FROM dba_profiles WHERE profile='DEFAULT'

find

FAILED_LOGIN_ATTEMPTS PASSWORD 10

In other words, the maximum number of password errors allowed is 10, and the account is automatically locked more than 10 times. So no matter how alter unlock is useless, we have to relax this restriction first.

Modify the limit parameter FAILED_LOGIN_ATTEMPTS to: unlimited

Sql > alter profile default limit FAILED_LOGIN_ATTEMPTS unlimited

Or modified to a larger number of times: 100000

Sql > alter profile default limit FAILED_LOGIN_ATTEMPTS 100000

Then execute the following

SQL > alter user test account unlock

SQL > conn smsdb/smsdb

You can log in normally.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.