Oracle11g cannot connect to the reported ORA-12537

A Windows Installation Oracle11g database, run for a period of time, suddenly encountered a ORA-12537 error, the application cannot connect.

An Oracle 11g database is installed on a Windows server. After running for a period of time, a ORA-12537 error suddenly occurs and the application cannot be connected.

An Oracle 11g database is installed on a Windows server. After running for a period of time, a ORA-12537 error suddenly occurs and the application cannot be connected. Check the alert. log file and find the following error message:

Fatal NI connect error 12537, connecting:
(LOCAL = NO)

Version information:
TNS for 32-bit Windows: Version 11.2.0.1.0-Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.2.0.1.0-Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 11.2.0.1.0-Production
Time: 2013 09:08:24
Tracing not turned on.
Tns error struct:
Ns main err code: 12537

TNS-12537: TNS: Connection closed
Ns secondary err code: 12560
Nt main err code: 0
Nt secondary err code: 0
Nt OS err code: 0
Opiodr aborting process unknown ospid (6032) as a result of ORA-609

Wed Mar 20 09:08:34 2013

This error message is continuously displayed in the log file alert. log. No system changes were made before the error occurred.

Because it is a windows system, there are some issues, and I don't know what the system will do. But the database is normal. Even if it is restarted, sysdba can still be used to log on. The problem must be in the listener. The listener cannot establish a connection with the database process.

Run the lsnrctl status Command to check the listener status. The result is no response.

According to the oracle prompt, modify the parameters of the listener. ora file and sqlnet. ora file.

Sqlnet. ora: SQLNET. INBOUND_CONNECT_TIMEOUT = 180
Listener. ora: INBOUND_CONNECT_TIMEOUT_LISTENER = 120

Set the timeout value to a greater value. The default value is 60 seconds.

However, it does not work. During this process, you do not know how many times the server has been restarted. Windows.

Later, I checked the listener. log File and suddenly found that the file size is 4 GB. The new content is no longer written.

If the log file is full, the listener will not work. As a result, the file is cleared and everything becomes normal.

I remember that in oracle 10 Gb in linux, once the log file is full, no logs are recorded but the listener is normal. I did not expect that in windows, 11G would be suspended.

Alas, details. Pay attention to the details.