Oracle unlocks the user, the lock reason, the location of the listening log file exists

-----Unlocking User Statements
Alter user Assp_test account unlock

-----1, the DBA role of the user login, unlock, first set the specific time format, in order to see the specific time
Alter session set nls_date_format= ' Yyyy-mm-dd hh24:mi:ss ';

-----2, check the specific lock time
Select Username,lock_date from dba_users where username= ' assp_test ';

-----3. Unlocking the user
Alter user Assp_test account unlock

-----4, check that the IP is the result of the test user is locked
The path to view Oracle9 is: $ORACLE _home/network/admin/log/listener.log log

Oracle11 path is: E:\app\wsw\diag\tnslsnr\wushuishui\listener\trace\listener.log log

10-mar-2009 08:51:03 * (Connect_data= (sid=lhoms) (server=dedicated) (Cid= (program=oracle) (HOST=OMSTESTDB) (USER= oraoms)) * (Address= (PROTOCOL=TCP) (host=10.69.1.11) (port=49434)) * Establish * lhoms * 0
10-mar-2009 08:51:03 * (Connect_data= (sid=lhoms) (server=dedicated) (Cid= (program=oracle) (HOST=OMSTESTDB) (USER= oraoms)) * (Address= (PROTOCOL=TCP) (host=10.69.1.11) (port=49435)) * Establish * lhoms * 0www.examda.com
This is known as the above 10.69.1.11 IP attempts to fail the landing caused by the lock
Note:
The general database defaults to 10 attempts to lock the user after a failure
1. View the value of the failed_login_attempts
SELECT * FROM Dba_profiles
2, modified to 30 times
Alter profile default limit failed_login_attempts 30;
3, modified to unlimited (for security purposes, not recommended)
Alter profile default limit Failed_login_attempts unlimited;

Oracle unlocks the user, the lock reason, the location of the listening log file exists