ORACLE 11g listening file log is too large, causing client connection failure problem yesterday, the client program actually appeared, no valid listening, unable to connect to the database, then view the WINDOWS Server ORACLE listening service, everything is normal, www.2cto.com has no problem. lsnrctl status, check the listening status, and find it is very slow. I stopped the previous listening. After creating a new listening, everything is normal and the client can be connected immediately, after checking the log today, we found that there are more than 4 GB listening log files under D: \ app \ administrator \ diag \ tnslsnr \ MACHINE name \ listenrt \ trace, and the log files are cleared, re-enable the original listener, and everything is normal. Ah, it turns out that this is the reason, because the listening log is too large, so the listener cannot run normally, WINDOWS platform said this problem is common.