Shulou(Shulou.com)05/31 Report--

This article mainly explains the "database connetion reset ora 3136 error analysis", the content of the article is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in depth, together to study and learn "database connetion reset ora 3136 error analysis" bar!

Error description: the platform is online these days, and the payment system will begin to be deployed to the production environment. System environment: linux centos 7.5 oracle11.2.0.4 java1.8. The java system has a total of 90 services, each with 2 database connections, which are started together and distributed among 90 virtual machines. When it is found that some machines connect to data, they get stuck and wait for a period of time, which may be 1 minute, 2 minutes, 10 minutes, or half an hour, and then the log prints the following error message:

Java.sql.SQLRecoverableException: IO Error: Connection reset at oracle.jdbc.driver.T4CConnection.logon (T4CConnection.java:533) at oracle.jdbc.driver.PhysicalConnection. (PhysicalConnection.java:557) at oracle.jdbc.driver.T4CConnection. (T4CConnection.java:233) at oracle.jdbc.driver.T4CDriverExtension.getConnection (T4CDriverExtension.java:29) at oracle.jdbc.driver.OracleDriver.connect (OracleDriver.java:556) at java. Sql.DriverManager.getConnection (DriverManager.java:579) at java.sql.DriverManager.getConnection (DriverManager.java:221) at test.jdbc.Main (Test.java:120) Caused by: java.net.SocketException: Connection reset at java.net.SocketOutputStream.socketWrite (SocketOutputStream.java:113) at java.net.SocketOutputStream.write (SocketOutputStream.java:153) at oracle.net.ns.DataPacket.send (DataPacket.java:248) At oracle.net.ns.NetOutputStream.flush (NetOutputStream.java:227) at oracle.net.ns.NetInputStream.getNextPacket (NetInputStream.java:309) at oracle.net.ns.NetInputStream.read (NetInputStream.java:257) at oracle.net.ns.NetInputStream.read (NetInputStream.java:182) at oracle.net.ns.NetInputStream.read (NetInputStream.java:99) at oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket (T4CSocketInputStreamWrapper.java At oracle.jdbc.driver.T4CSocketInputStreamWrapper.read (T4CSocketInputStreamWrapper.java:77) at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1 (T4CMAREngine.java:1173) at oracle.jdbc.driver.T4CTTIfun.receive (T4CTTIfun.java:309) at oracle.jdbc.driver.T4CTTIfun.doRPC (T4CTTIfun.java:200) at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY (T4CTTIoauthenticate.java:404) at oracle.jdbc.driver.T4CConnection .logon (T4CConnection.java:430)... 35 more

Check the log of oracle and find the following error:

Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.4.0-Production Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0-Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0-Production Time: 17-SEP-2018 13:54:01 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12606 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Client address: (ADDRESS= (PROTOCOL=tcp) (HOST=10.14.254.99) (PORT=51492)) WARNING: inbound connection timed out (ORA-3136)

Occasionally, one or two machines make a large number of database empty connection requests. My connection login log dba _ audit_trail on oracle has the following statistics:

Database login error: null password given; logon denied:

Second, these two problems are the most difficult, it is difficult to track: the problem is occasional, and 90 machines request databases, some machines can connect quickly, some reports time out.

Have you figured out what I'm talking about so far? Currently, there are two problems: 1.java application connection startup timeout, connection reset, oracle log report WARNING: inbound connection timed out (ORA-3136). 2. Initiating a large number of database connection empty requests null password given; logon denied. In fact, the hardest thing to track about these two problems is that errors occur from time to time. For example, problem 1, the connection timed out, started 5 times, maybe the 6th time connection can immediately connect to the database. Problem 2, not every startup is caused by a large-scale error in initiating an empty connection request. But sometimes.

Thank you for your reading, the above is the content of "Database connetion reset ora 3136 error Analysis". After the study of this article, I believe you have a deeper understanding of the problem of database connetion reset ora 3136 error analysis, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.