Oracle Login Error ora-28000:the account is locked

Ora-28000:the account is locked
The first step: using PL/SQL, the login name is system, the database name is not changed, select the type of time to change the normal to SYSDBA;
The second step: select Myjob, view users;
Step three: Select System, right click on "edit";
Fourth step: Change the password, the "account is locked" tick off;
Fifth step: Click "Apply" and click "Close";
The sixth step: re-login can be verified by;
The second Kind
ALTER USER username account UNLOCK;

Third Kind

In Plsql Developer If you are logged in with Scott/tiger, ora-28000 the account is locked.

Workaround:

After the newly installed oracle10g, with the Scott/tiger test, the following error message will appear:
oracle10g the account is locked
oracle10g the password has expired
Cause: The default oracle10g Scott cannot log in.
Solve:
(1) Conn Sys/sys as SYSDBA; Log in as a DBA
(2) Alter user Scott account unlock;//then unlock
(3) Conn Scott/tiger//Popup A Password Change dialog box, modify the password can be

In the run input cmd in the DOS mode input sqlplus, the system user name login, password is just loaded Oracle self-filled password orcl, log in after.

Sql> Conn Sys/sys as SYSDBA; (Semicolons are required but I am logged in as system this should not be written Conn Sys/sys as SYSDBA should write Conn SYSTEM/ORCL as SYSDBA;)
Connected.
sql> alter user Scott account unlock;
User altered.
Sql> commit;
Commit complete.
Sql> Conn scott/tiger//Please enter a new password and confirm the OK
Password changed
Connected.

At this time again to plsql developer inside to Scott/tiger login on it can be .....

I encountered the problem in the database processing ora-28000:the account is locked error, the details of the process is described below for your reference:

1. Query the default value of the Failed_login_attempts parameter:
Oracle10g( Note: The value of this parameter in a 9i environment is unlimited)

Sql>conn/as SYSDBA

Connected.

sql> desc dba_profiles;
is the name empty? Type
----------------------------------------- -------- --------------

Profile is not NULL VARCHAR2 (30)
Resource_name not NULL VARCHAR2 (32)
Resource_type VARCHAR2 (8)
LIMIT VARCHAR2 (40)

Sql> Select Resource_name,limit from dba_profiles where resource_name= ' failed_login_attempts ';

Resource_name LIMIT
-------------------------------- ----------------------------------------
Failed_login_attempts 10

2. Demo account is locked
(Modify default profile failed_login_attempts=3 for easy simulation of lock phenomenon)
A. Modifying the parameter failed_login_attempts=3

Sql> Conn/as SYSDBA
is connected.
sql> alter profile default limit failed_login_attempts 3;

Configuration file has changed

Sql> Select Resource_name,limit from dba_profiles where resource_name= ' failed_login_attempts ';

Resource_name LIMIT
-------------------------------- ----------------------------------------
Failed_login_attempts 3

B. Reproduce the error login
Correct login

Sql> Conn JD/JD
is connected.

First logon failure
Sql> Conn Jd/jh
ERROR:
Ora-01017:invalid Username/password; Logon denied

Warning: You are no longer connected to ORACLE.

Second Landing failed
Sql> Conn Jd/ju
ERROR:
Ora-01017:invalid Username/password; Logon denied

Third Logon failure

Sql> Conn JD/JL
ERROR:
Ora-01017:invalid Username/password; Logon denied

After three consecutive failed logins, the account is locked

Sql> Conn Jd/jy
ERROR:
Ora-28000:the account is locked

3. Unlocking

Sql> Conn/as SYSDBA
is connected.
Sql> ALTER user JD account unlock;

The user has changed.

4. Solution
(1) Can consider querying the application deployment in the wrong password or database connection, etc. may lead to error password place, thoroughly query the problem.
(2) Modify the parameter failed_login_attempts=unlimited

sql> alter profile default limit Failed_login_attempts unlimited;

Configuration file has changed

Sql> Select Resource_name,limit from dba_profiles where Resource_name= ' Failed_lo
Gin_attempts ';

Resource_name LIMIT
-------------------------------- ----------------------------------------
Failed_login_attempts UNLIMITED

5. Extended Knowledge points and notes
(1) What is the meaning of q:failed_login_attempts=3 3? Is it cumulative failure or consecutive number of failures?
The meaning of a:failed_login_attempts=3 is the number of consecutive login failures that have been calculated from the first login failure. Rather than the number of cumulative failures.
The test is as follows:

Sql> Conn/as SYSDBA
is connected.
sql> alter profile default limit failed_login_attempts 3;

Configuration file has changed

Sql> Conn JD/JD
is connected.

First logon failure
Sql> Conn Jd/jh
ERROR:
Ora-01017:invalid Username/password; Logon denied

Warning: You are no longer connected to ORACLE.

Second Landing failed
Sql> Conn Jd/gh
ERROR:
Ora-01017:invalid Username/password; Logon denied

Login is correct

Sql> Conn JD/JD
is connected.

First logon failure
Sql> Conn JD/DF
ERROR:
Ora-01017:invalid Username/password; Logon denied

Warning: You are no longer connected to ORACLE.

Second Landing failed
Sql> Conn JD/SD
ERROR:
Ora-01017:invalid Username/password; Logon denied

Third Logon failure

Sql> Conn JD/FG
ERROR:
Ora-01017:invalid Username/password; Logon denied

The user is locked out after three login failures

Sql> Conn JD/HJ
ERROR:
Ora-28000:the account is locked

(2) Q: How can I query the value of the current failed_login_attempts from the database? Dba_profiles is the limit and does not represent the current value, what if the query is currently failing?
A:select Name,lcount from user$,user$ is the base table for view dba_users, and you can usually query the base table that you are trying to match, and Oracle may hide some parameters.

Oracle Login Error ora-28000:the account is locked