Solution to Oracle database account locking

During Oracle database manipulation, an error is prompted when logging on to the Oracle account, and the Oracle account is frequently locked. What are the causes of this fault? This article introduces this process and finds the cause of the fault through further troubleshooting.
Next we will record the pace of searching for this question.
1. When the account is locked
When the query account is locked, the related statement is as follows:
-- Correct the date display pattern of the current session
Alter session set nls_date_format = "" yyyy-MM-dd hh24: mi: ss "";
-- Query the lock times of the locked account
Username, lock_date dba_users where username like "" TRSEKPV65_DEMO "";
For example, the query locks are: 20: 03: 03.

2. Find the installation directory of oracle
The oracle installation path for the project team knowledge library is: C: \ devsoftware \ oracle11g

3. Find the monitoring log
Find
C: \ devsoftware \ oracle11g \ diag \ tnslsnr \ DEV2-216 \ listener \ trace \ listener. log file, which records some tracking information of oracle

4. view the monitoring log
After the file is found, it is very invented and cannot be opened with editplus. Upload the file to linux to download a tail.exe Method on Windows host. Execute the tail-20 listener. log command to view the last 20 lines of the file.

5. Locate a question
Find the corresponding time position in the diary according to the time found above, and you can locate the operation performed by Oracle at the current time.
-2011 20:03:35 * (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = portalteam) (CID = (PROGRAM = D: \ TRS \ TRSGateway4.6 \ gwserver_x64 \ TrsAgent.exe) (HOST = DEV2-216) (USER = Administrator) * (ADDRESS = (PROTOCOL = tcp) (HOST = fe80: e816: 9e03: 60ac: fdaa % 11) (PORT = 13678) * establish * portalteam * 0

6. Summary
We can see from the above that the reason for Oracle account locking is caused by the "TrsAgent.exe" process. After careful consideration, I corrected the password and did not correct the GateWay login information. As a result, this account often fails to log on to Oracle because the maximum number of allowed logon errors on Oracle is 10, therefore, the account will be locked after 10 errors.