Shulou(Shulou.com)06/02 Report--

1. Description of the environment:

OS: Windows Server 2008 32Bit

DB: 11.2.0

Second, the troubleshooting process:

The day before yesterday, the application can not access the database (background applications can access the database), failure occurred.

Log in to the server immediately to check the monitoring status and find errors such as TNS-12541, TNS-12560 and so on.

Start the listening service manually, and the service status shows that it has been started, but an error message is still returned when the CMD window executes lsnrctl status:

C: lsnrctl statusLSNRCTL for 32-bit Windows: Version 11.2.0.1.0-Production on 13-February-2018 10:39:47Copyright (c) 1991, 2010, Oracle. All rights reserved. Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=TCP) (HOST=john-PC) (PORT=TNS-12541: TNS: no listener TNS-12560: TNS: protocol adapter error TNS-00511: no listener 32-bit Windows Error: 61: Unknown error is connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC1521) echo is very slow after a period of time. III. Solution steps

* * there is a case of solving TNS-12535 errors on the Internet. The platform and version are similar, as follows:

1. Add the following line to the sqlnet.ora file:

DIAG_ADR_ENABLED = OFF

2. Add the following line to the listener.ora file: DIAG_ADR_ENABLED_ = OFF. If the listening is listener, the preceding name is: DIAG_ADR_ENABLED_LISTENER = OFF.

3. Restart the listener in windows service management. Stop first, and then restart. 4, check the results. It is found that it is OK, and the value returned is 10 milliseconds. Sometimes it is 0 millisecond. Success!

However, this is not the cause of the problem. In the course of continuing the investigation, we accidentally found that the size of the monitoring log was 4G.

Oracle A BUG,BUG number is 9879101: THE CONNECT THROUGH LISTENER WAS SLOW WHEN LISTNER LOG GROWED 4GB.

There is a previous MOS article, ID 1319797.1: WINDOWS: Listener Hangs & Lsnrctl Commands Are Slow or Hang, which gives a solution:

You can solve this problem by deleting the large listener in $ORACLE_BASE\ diag\ tnslsnr\\ listener\ trace\ .log1) Stop the listener process using the command line or Control Panel Service.2) Delete the log file (s) that are at or approaching the 4G size limit at this location:$ORACLE_BASE\ diag\ tnslsnr\\ listener\ trace\ .log3) Issue any lsnrctl command and you will see a new listener.log in its place under:$ORACLE_BASE\ diag\ tnslsnr\ listener\ trace\ Since ADR Diagnostics are enabled for this listener these steps cannot be done dynamically using the lsnrctl utility. E.g.LSNRCTL > set log_file mylogWill yield: TNS-01251: Cannot set trace/log directory under ADR.However, it is possible to disable the flat file listener logging using the following commands:LSNRCTL > set current_listener LSNRCTL > set log_status OFFLSNRCTL > save_config5, as described above:

1) LSNRCTL enters interactive mode

2) set log_file mylog

3) execute set current_listener LISTENER

4) set log_status off

5) save_config

6) stop stop listener

7) manually delete the listener.log file under the listening log path specified by ADR

8) start restart listener

9) status view status

By the time the problem is solved.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.