WINDOWS: Listener Hangs & Lsnrctl Commands Are Slow or Hang
(Doc ID 1319797.1)
Last updated on JANUARY 16, 2025
Applies to:
Oracle Net Services - Version 11.1.0.7 and laterOracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Microsoft Windows x64 (64-bit)
Microsoft Windows (32-bit)
This issue is limited to the Windows OS.
Symptoms
- The listener is hung or is extremely slow to respond.
- Tnspings to the listener take a very long time (seconds) to respond or the ping hangs completely.
- Lsnrctl utility commands are either hanging or slow to respond.
- ADR Diagnostics are enabled in this environment and the flat file TNSListener log file is at or approaching the size of 4 gigabytes.
Check this location: $ORACLE_BASE\diag\tnslsnr\<hostname>\listener\trace\
The listener.log might contain messages similar to the following DBGRL error being repeated throughout:
Or the lsnrctl status command might hang altogether. In other words, lsnrctl status or services is unresponsive.
Changes
No recent changes have taken place on this server. It is likely that this installation has been in place for some time as the listener.log has grown to at or near 4G in size. It is also likely that ADR diagnostic for the listener is enabled on this server. i.e. No DIAG_ADR_<listener_name>=OFF in listener.ora.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |