User Smsdb in Oracle cannot log in LOCKED (TIMED)

Create a user smsdb, view status locked (TIMED)

UNLOCKED, conn Smsdb/password still error, and then locked, and finally found that the number of errors to reach the Oracle limit of 10 times, resulting in subsequent failure to log on operation. Here's how to find the solution online:

Look at information such as the user's status in dba_users

Sql>select account_status,lock_date,profile from Dba_users where username= ' smsdb ';
Found yesterday only locked, the account status of "LOCKED (TIMED)", is the number of password errors more than the maximum number of system settings allowed.
View the maximum number of times now set
SELECT resource_name,resource_type,limit from Dba_profiles WHERE profile= ' DEFAULT ';
Found it
Failed_login_attempts PASSWORD 10
That is, the original maximum number of password errors allowed is 10 times, more than 10 auto-lock account. So how to alter unlock is useless, we must first put this restriction to relax.
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 do the following
Sql>alter user test account unlock;
Sql>conn Smsdb/smsdb

will be able to log in normally.

This article is from the "10999243" blog, please be sure to keep this source http://11009243.blog.51cto.com/10999243/1794610

User Smsdb in Oracle cannot log in LOCKED (TIMED)