Troubleshoot frequent Oracle database account locking

InOracle DatabaseAn error occurred while logging on to the Oracle account.Account locked frequently. What are the causes of this fault? This article introduces this process and finds the cause of the fault through gradual troubleshooting.

Next, record the steps for finding this problem.

1. Find the account lock time

Use sqlplus or sqldeveloper to query the account lock time. The related statements are as follows:

-- Modify the date display format of the current session

Alter session set nls_date_format = 'yyyy-MM-dd hh24: mi: ss ';

-- Query the lock time of the locked account

Select username, lock_date from dba_users where username like 'trsekpv65 _ demo ';

For example, the queried lock time is: 20: 03: 03.

2. Find the installation directory of oracle

The oracle installation path for the department knowledge base is: C: \ devsoftware \ oracle11g

3. Find the listening log

Find

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

4. View listening logs

The file is found to be large and cannot be opened with editplus. Upload the file to linuxlinux and download a tail.exe program on Windows Server. Run the tail-20 listener. log command to view the last 20 lines of the file.

5. Locate the problem

Based on the time found above, find the corresponding time location in the log and locate the operations 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, the original password was changed and the GateWay login information was not modified, which caused frequent logon failures of this account to Oracle. As we configured the maximum number of allowed logon Errors for Oracle to be 10, therefore, the account will be locked after more than 10 errors.

The solution to the problem of frequent Oracle database account locking is introduced here. If you want to learn more about Oracle databases, you can read the article here: http://database.51cto.com/oracle/. it is a reliable solution for you!