Shulou(Shulou.com)06/01 Report--

Such error logs are often found in logs during Oracle database inspections, but usually do not affect customer usage.

The overall error is as follows:

*********************************************************************** 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: 30-JUN-2020 09:59:59 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 nt main err code: 505 TNS-00505: Operation timed out nt secondary err code: 110 nt OS err code: 0

By viewing the official documentation:

ORA-12170: TNS:Connect timeout occurredCause: The client failed to establish a connection and complete authentication in the time specified by the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in the sqlnet.ora file. This error may be a result of network or system delays, or it may indicate that a malicious client is trying to cause a denial-of-service attack on the database server.

This means:

TNS Connection Timeout

The reason is that the client was unable to establish a connection and complete authentication within the specified time. Parameter sqlnet.ora file in SQLNET.INBOUND CONNECT timeout. This error may be due to network or system latency, or it may indicate that a malicious client is attempting to cause a denial of service attack on the database server.

From the final result of the database can still be used normally, this is caused by the delay. According to the relevant error handling methods on the Internet. Since Oracle Net diagnostic is on in the Automatic Diagnostic Repository, connection delay errors are captured and written to the alert log. The solution is to turn off the configuration of automatic diagnosis about network diagnosis.

In fact, the whole error report has no effect. If there is no special demand, it can not be closed.

Refer to the solution on the network:

[Solution]

[oracle@node1 ~]$ lsnrctl statusLSNRCTL for Linux: Version 11.2.0.1.0 - Production on 02-MAR-2015 12:34:22Copyright (c) 1991, 2009, Oracle. All rights reserved.Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for Linux: Version 11.2.0.1.0 - ProductionStart Date 02-MAR-2015 09:45:49Uptime 0 days 2 hr. 48 min. 33 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Parameter File /u01/11.2.0/grid/network/admin/listener.oraListener Log File /u01/app/oracle/diag/tnslsnr/node1/listener/alert/log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.53.105.20)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.53.105.24)(PORT=1521)))Services Summary... Service "+ASM" has 1 instance(s). Instance "+ASM1", status READY, has 1 handler(s) for this service... Service "xcky" has 1 instance(s). Instance "xcky1", status READY, has 1 handler(s) for this service... Service "xckyXDB" has 1 instance(s). Instance "xcky1", status READY, has 1 handler(s) for this service... The command completed successfully[oracle@node1 ~]$ cd /u01/11.2.0/grid/network/admin/[oracle@node1 admin]$ lsendpoints_listener.ora listener.ora samples sqlnet.oralistener1410255PM1539.bak listener. ora.bak.node1 shrept.lst[root@node1 admin]#chmod 775 listener.ora[root@node1 admin]#chmod 775 sqlnet.ora--Confirm oracle user access to configuration files [@ oracle] node1 admin]$ vi listener.ora--add parameter INBOUND_CONNECT_TIMEOUT_LISTENER = 0--add parameter DIAG_ADR_ENABLED_LISTENER = OFLISTENER =(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))) # line added by AgentLISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1)))) # line added by AgentENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON # line added by AgentENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON # line added by AgentINBOUND_CONNECT_TIMEOUT_LISTENER = 0DIAG_ADR_ENABLED_LISTENER = OFF~~[oracle@node1 admin]$ vi sqlnet.ora--add parameter DIAG_ADR_ENABLED = OFF--add parameter SQLNET.INBOUND_CONNECT_TIMEOUT = 0#sqlnet.ora.node1 Network Configuration File: /u01/11.2.0/grid/network/admin/sqlnet.ora.node1# Generated by Oracle configuration tools.NAMES.DIRECTORY_PATH=(TNSNAMES, EZCONNECT)ADR_BASE = /u01/app/oracleDIAG_ADR_ENABLED = OFFSQLNET.INBOUND_CONNECT_TIMEOUT =0

Reference link: https://blog.csdn.net/huangyanlong/article/details/46372849

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.