Oracle 11g cannot connect to reporting ORA-12537 + ora-609 resolution, ora-12537ora-609

Oracle 11g cannot connect to reporting ORA-12537 + ora-609 resolution, ora-12537ora-609

Operating System: windows2008

Database: oracle11g

Problem: an application system that has been running normally for a year suddenly cannot connect to the database, but another application can be linked normally, and data is stored in the database normally.

 

Database Server View:

You can use lsnrctl status to check whether the listener is stuck. The results will be reported in about 10 minutes.

Plsql cannot be connected.

The restart listening problem persists.

An error is reported in the alter log file:

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

Version information:
TNS for 64-bit Windows: Version 11.2.0.1.0-Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0-Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0-Production
Time: 17-6-2015 09:17:49
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 (6052) as a result of ORA-609

 

Use sqlplus on the dos side to log on normally. Check the latest data for Database Import. Suspected to be a listener problem!

 

View the listening log File $ ORACLE_HOME/network/log. The error is as follows:

<Msg time = '2017-06-16T02: 14: 2015 + 08: 00' org_id = 'oracle 'comp_id = 'tnslsnr'
Type = 'unknown 'level = '16' host_id = 'windows-35NMUNE'
Host_addr = 'fe80: 7840: 6685: 828f: 4f5a % 17'>
<Txt> TNS-12560: TNS: protocol adapter Error
TNS-00530: protocol adapter Error
64-bit Windows Error: 53: Unknown error
TNS-12518: TNS: Listeners cannot distribute client connections
TNS-12571: TNS: Package write failed
TNS-12560: TNS: protocol adapter error.
TNS-00530: protocol adapter Error
64-bit Windows Error: 54: Unknown error
</Txt>
</Msg>

An error occurs when the ora-12518 listener cannot distribute client connections. However, in oracle, the show parameter session and select count (×) from v $ session are used. The comparison shows that this is not a connection limit problem.

Using tnsping IP does not respond.

 

Then, view the listener log File $ ORACLE_HOME/network/trace and find listener. the log file reaches 4 GB and cannot be written again. The last write date is two days earlier. Therefore, the log file is deleted and the listener is started. Normal ~!!

 

The final cause is that the log file is full. It seems that the file will be cleaned regularly in the future. Such a small problem makes the application system unable to connect, and the Details determine success or failure. For such files, you must record one file and check it in a similar system.