Oracle Login Database times No listening to a solution (listening log file reached the default limit of 4g)

Issue: Login server times No monitoring service

Check the steps:

1. Enter Sqlplus to view the status of the database, showing that the current database status is open

Script: Select status from V$instance;

2, check the database monitoring service, log in to find that the speed of entering the listener is very slow

Script: Lsnrctl Status

3, check the size of the listening log, the location is as follows:

$ORACLE _base\diag\tnslsnr\

5, restart the monitoring can be started;

Lsnrctl Stop Stop

Lsnrctl start

6, the current problem has been resolved, to ensure that the system can operate normally, but this is a palliative approach to the root causes, and therefore log metalink to find the appropriate solution, the following excerpt from Metalink:

1) The cause of the problem: when the Listener.log size reaches 4G

The Listener.log has reached the file size limit (on Windows) of 4G. This issue was described in published bug:
bug:9879101 The CONNECT THROUGH LISTENER is SLOW when LISTENER LOG GREW to 4GB

2) the platform on which the bug occurred

Oracle Net services-version 11.1.0.7 to 11.2.0.4 [Release 11.1 to 11.2]

Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
This issue was limited to the Windows OS.
Checked for relevance on 14-oct-2013***

3) Symptoms of this bug appear

The listener is hung or was extremely slow to respond.
Tnspings to the listener take a very long time (seconds) to respond or the ping hangs completely.
Lsnrctl Utility Commands is either hanging or slow to respond.
ADR Diagnostics is enabled with this environment and the flat file Tnslistener log file was at or approaching the size of 4 Gigabytes.

4) Workaround: Turn off the Listen write log

Script:

Lsnrctl>set Current_listener <listener_name>
Lsnrctl>set Log_status OFF
Lsnrctl>save_config

Oracle Login Database times No listening to a solution (listening log file reached the default limit of 4g)