Oracle 11g R2 Monitor file log under Windows platform is too large, causing the client to be unable to connect problem handling

Applications that have recently been deployed in a production environment are suddenly inaccessible, and viewing the application log finds that the database connection could not be obtained.

systemerr R caused by:oracle.net.ns.NetException:The Network Adapter could not establish the Connectionsystemerr R at Oracle.net.nt.ConnStrategy.execute (Connstrategy.java:359) Systemerr R at Oracle.net.resolver.AddrResolution.resolveAndExecute (Addrresolution.java:422) Systemerr R at Oracle.net.ns.NSProtocol.establishConnection (Nsprotocol.java:672) Systemerr R at Oracle.net.ns.NSProtocol.connect (Nsprotocol.java:237) Systemerr R at Oracle.jdbc.driver.T4CConnection.connect (T4cconnection.java:1042) Systemerr R at Oracle.jdbc.driver.T4CConnection.logon (T4cconnection.java:301) Systemerr R ...154  MoreSystemerr R caused by:java.net.ConnectException:Connection refused:connectsystemerr R at Java.net.DualS Tackplainsocketimpl.waitforconnect (Native Method) Systemerr R at Java.net.DualStackPlainSocketImpl.socketConnect (Du Alstackplainsocketimpl.java: the) Systemerr R at Java.net.AbstractPlainSocketImpl.doConnect (Abstractplainsocketimpl.java:369) Systemerr R at Java.net.AbstractPlainSocketImpl.connectToAddress (Abstractplainsocketimpl.java: the) Systemerr R at Java.net.AbstractPlainSocketImpl.connect (Abstractplainsocketimpl.java:212) Systemerr R at Java.net.PlainSocketImpl.connect (Plainsocketimpl.java:191) Systemerr R at Java.net.SocksSocketImpl.connect (Sockssocketimpl.java:403) Systemerr R at Java.net.Socket.connect (Socket.java:642) Systemerr R at Oracle.net.nt.TcpNTAdapter.connect (Tcpntadapter.java:141) Systemerr R at Oracle.net.nt.ConnOption.connect (Connoption.java:123) Systemerr R at Oracle.net.nt.ConnStrategy.execute (Connstrategy.java:337) Systemerr R ...159  More

Operation Record:

1, restart the database monitoring, the instance service still cannot connect through the client;

2, restart the database server after the start of monitoring and the instance service is still unable to connect;

3, the attempt to use the Client Connection tool in the server connection to the database can not get connections, the possibility of troubleshooting network problems;

4. After the app is stopped connected to the database server, the listening and instance service can start normally, and the client can connect to the database server.

5, at this time through the EXP command to the database data backup;

6. After launching the app connected to this database, it is found that the connection still cannot be obtained, and the Oracle instance is connected through the client tool again.

7, stop the application again, try to restart the Oracle service several times finally started up;

8, after the backup data is imported to the backup database server, the database connection of the application is switched to the backup database, and the normal service is restored;

Troubleshoot issues :

1, to eliminate the possibility of network failure;

2, check the monitoring file configuration is correct;

Path: D:\app\Administrator\product\11.2.0\dbhome_1\NETWORK\ADMIN\listener.ora

3, check tnsnames configuration is correct;

Path: D:\app\Administrator\product\11.2.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora

4, check the error log;

Path: D:\app\Administrator\diag\rdbms\orcl\orcl\trace\alert_orcl.log

A large number of errors are found by viewing the log:

tns-12537: TNS: Connection off     12560    0    0      0

By Baidu error keyword "Tns-12537:tns: Connection Close", found an article:

http://blog.itpub.net/23169974/viewspace-1067401/

This article describes the problem that the Listener.log log file is too large to cause a service exception, and feels like my own.

5. View Listener.log Log

The file was finally found by searching the log file.

Path: D:\app\Administrator\diag\tnslsnr\WIN-RU03CB21QGA\listener\trace\listener.log

found that the file did grow to 4GB in size, consistent with the problem described in the blog, and finally found the problem.

Problem handling:

The solution is simply to stop all Oracle services, clear the log files, and restart the service.

Oracle 11g R2 Monitor file log under Windows platform is too large, causing the client to be unable to connect problem handling