Operating system: windows2008
Database: oracle11g
Problem occurs: A set of normal run a year of application system, suddenly unable to connect to the database, but another application can be normal link, data storage normal.
Database server-side view:
Use Lsnrctl status to view the listening status of the card, 10 minutes or so before the results will be feedback.
Plsql cannot connect.
Restart monitoring is still the problem.
An error in the Alter log file:
Fatal NI Connect error 12537, connecting to:
(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 Month-2015 09:17:49
Tracing not turned on.
Tns error struct:
NS Main ERR code:12537
Tns-12537:tns: Connection off
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 DOS side sqlplus login is normal, check the latest data storage. Suspicion is a listening problem!
Check the log file $ORACLE _home/network/log error is as follows
<msg time= ' 2015-06-16t02:14:18.877+08:00 ' org_id= ' Oracle ' comp_id= ' Tnslsnr '
Type= ' UNKNOWN ' level= ' 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: Listener fails to distribute client connections
Tns-12571:tns: Package writer failed
TNS-12560:TNS: Protocol Adapter error
TNS-00530: Protocol Adapter error
64-bit Windows Error:54:unknown Error
</txt>
</msg>
Error ora-12518 listener failed to distribute client connections. However, use show parameter session with select COUNT (x) from v$session in Oracle; Comparison finds not a connection number limit issue.
There is no response using the tnsping IP.
After continuing to view the Listener log file $ORACLE _home/network/trace found Listener.log file has reached 4G can not continue to write, the last write date is also two days ago, so delete the log file, start monitoring, normal ~!!
The final reason to find that the log file is full, it seems to be regularly cleaned up this file. Such a small problem makes the application system unable to connect, the details determine success or failure. Such files are to be seen in one record at a time in a similar system.
Oracle 11g cannot connect to ora-12537+ora-609 solution