TNS-12535: TNS:operation timed out、TNS-00505: Operation timed out

在查看alert日志的时候发现:


 1 ***********************************************************************
2
3 Fatal NI connect error 12170.
4
5 VERSION INFORMATION:
6 TNS for Linux: Version 11.2.0.1.0 - Production
7 Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
8 TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
9 Time: 27-DEC-2012 16:17:46
10 Tracing not turned on.
11 Tns error struct:
12 ns main err code: 12535
13
14 TNS-12535: TNS:operation timed out
15 ns secondary err code: 12560
16 nt main err code: 505
17
18 TNS-00505: Operation timed out
19 nt secondary err code: 110
20 nt OS err code: 0
21 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.xxx)(PORT=xxxx))
22 Thu Dec 27 16:46:44 2012
23
24
25 ***********************************************************************

参考官方说明关于该警告的说明:

Note:465043.1

The "WARING:inbound connection timed out (ORA-3136)" in the
alert log indicates that the client was not able to complete it‘s authentication
within the period of time specified by parameter
SQLNET.INBOUND_CONNECT_TIMEOUT.

You may also witness ORA-12170 without timeout error on the
database sqlnet.log file.This entry would also have the client address which
failed to get authenticated.Some applications or JDBC thin driver applications
may not have these details.

可能的原因:

1、网络攻击,例如:半开连接攻击

Server gets a connection request from a malcious
client which is not supposed to connect to the database,in which case the error
thrown is the correct behavior.You can get the client address for which the
error was thrown via sqlnet log file.

2、Client在default 60秒内没有完成认证

The server receives a valid client connection request but
the client tabkes a long time to authenticate more than the default 60
seconds.

3、DB负载太高

The DB server is heavily loaded due to which it cannot
finish the client logon within the timeout specified.

WANGING:inbound connection timed out (ORA-3136)

解决问题:

其实这个参数跟监听的一个参数有关:SQLNET.INBOUND_CONNECT_TIMEOUT

这个参数从9i开始引入,指定了客户端连接服务器并且提供认证信息的超时时间,如果超过这个时间客户端没有提供正确的认证信息,服务器会自动中止连接请求,同时会记录试图连接的IP地址和ORA-12170:TNS:Connect
timeout occurred错误。

这个参数的引入,主要是防止DoS攻击,恶意攻击者可以通过不停的开启大量连接请求,占用服务器的连接资源,使得服务器无法提供有效服务。在10.2.0.1起,该参数默认设置为60秒。

但是,这个参数的引入也导致了一些相关的Bug。比如:

Bug 5594769 - REMOTE SESSION DROPPED WHEN LOCAL SESSION
SHARED AND INBOUND_CONNECT_TIMEOUT SET

Bug 5249163 - CONNECTS REFUSED BY TNSLSNR EVERY 49 DAYS
FOR INBOUND_CONNEC_TIMEOUT SECONDS

该参数可以通过设置为0来禁用,在服务端:

1)、设置sqlnet.ora文件:SQLNET.INBOUND_CONNECT_TIMEOUT=0;

2)、设置listener.ora文件:INBOUND_CONNECT_TIMEOUT_listenername=0;

3)、然后reload或者重启监听。

说明:这是由于连接超时所产生的问题,在10.2.0.1.0版本中sqlnet.inbound_connect_timeout参数默认为60秒,即如果连接时间超过60秒则提示超时,而在其他版本中这两个参数默认为0,即无限制。

具体操作例子:


 ----因为之前修改了很多次参数,一直没成功,这次就索性把监听给停掉了----------------
1 [[email protected] admin]$ lsnrctl stop
2
3 LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 27-DEC-2012 22:40:24
4
5 Copyright (c) 1991, 2009, Oracle. All rights reserved.
6
7 Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=xxxx)))
8 The command completed successfully
----在sqlnet.ora文件中添加SQLNET.INBOUND_CONNECT_TIMEOUT = 0----------
9 [[email protected] admin]$ vi sqlnet.ora
10 # sqlnet.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/sqlnet.ora
11 # Generated by Oracle configuration tools.
12
13 NAMES.DIRECTORY_PATH= (TNSNAMES)
14 SQLNET.INBOUND_CONNECT_TIMEOUT = 0
15

----在listener.ora文件添加INBOUND_CONNECT_TIMEOUT_listener=0------------
16 [[email protected] admin]$ vi listener.ora
17
18 # listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
19 # Generated by Oracle configuration tools.
20
21 LISTENER =
22 (DESCRIPTION_LIST =
23 (DESCRIPTION =
24 (ADDRESS = (PROTOCOL = TCP)(HOST = cnbpi)(PORT = xxxx))
25 # (CONNECT_TIMEOUT_LISTENER = 3600) -------该参数在测试中不起作用
26 )
27 )
28 INBOUND_CONNECT_TIMEOUT_listener=0
29
30 [[email protected] admin]$ lsnrctl
31
32 LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 27-DEC-2012 22:42:14
33
34 Copyright (c) 1991, 2009, Oracle. All rights reserved.
35
36 Welcome to LSNRCTL, type "help" for information.
37
-----因为监听已经停止,所以查不出inbound_connect_timeout参数是否修改成功----------------
38 LSNRCTL> show inbound_connect_timeout
39 Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cnbpi)(PORT=1521)))
40 TNS-12541: TNS:no listener
41 TNS-12560: TNS:protocol adapter error
42 TNS-00511: No listener
43 Linux Error: 111: Connection refused
44 LSNRCTL> set inbound_connect_timeout 0
45 Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cnbpi)(PORT=1521)))
46 TNS-12541: TNS:no listener
47 TNS-12560: TNS:protocol adapter error
48 TNS-00511: No listener
49 Linux Error: 111: Connection refused
----启动监听-----------------------------------
50 LSNRCTL> start
51 Starting /u01/app/oracle/product/11.2.0/db_1/bin/tnslsnr: please wait...
52
53 TNSLSNR for Linux: Version 11.2.0.1.0 - Production
54 System parameter file is /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
55 Log messages written to /u01/app/oracle/diag/tnslsnr/cnbpi/listener/alert/log.xml
56 Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=cnbpi)(PORT=xxxx)))
57
58 Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cnbpi)(PORT=xxxx)))
59 STATUS of the LISTENER
60 ------------------------
61 Alias LISTENER
62 Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
63 Start Date 27-DEC-2012 22:42:37
64 Uptime 0 days 0 hr. 0 min. 0 sec
65 Trace Level off
66 Security ON: Local OS Authentication
67 SNMP OFF
68 Listener Parameter File /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
69 Listener Log File /u01/app/oracle/diag/tnslsnr/cnbpi/listener/alert/log.xml
70 Listening Endpoints Summary...
71 (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=cnbpi)(PORT=xxxx)))
72 The listener supports no services
73 The command completed successfully
----查看inbound_connect_timeout参数已经修改成功,值为0-------------------
74 LSNRCTL> show inbound_connect_timeout
75 Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=xxxx)))
76 LISTENER parameter "inbound_connect_timeout" set to 0
77 The command completed successfully
-----因为之前在修改中可能是参数设置不对,所以一直没成功,所以用了这种最笨的方法使监听停掉以后再修改,其实只需修改了参数以后再reload一下就可以了。

参考文档:

http://www.cnblogs.com/diyunpeng/archive/2010/11/12.html

http://wenku.baidu.com/view/190df4aad1f34693daef3ee6.html

TNS-12535: TNS:operation timed out、TNS-00505: Operation timed
out

时间: 2024-10-21 09:34:11

TNS-12535: TNS:operation timed out、TNS-00505: Operation timed out的相关文章

ssh启动报错:org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect

ssh项目启动报错: org.dom4j.DocumentException: Connection timed out: connect Nested exception: Connection timed out: connect 一开始以为是数据库连接的事,后来发现是hibernate在实体对象映射数据库表的时候出的错 解决: 查看hibernate.jar包里的hibernate-mapping-3.0.dtd里的 <!DOCTYPE hibernate-mapping PUBLIC &qu

一组相关联的问题:“sudo: unable to resolve host ###: Connection timed out”、软件启动速度超慢、IPv6无法使用

近日陆续发现计算机出现几个问题,最终发现这些问题实际上是由同一个原因导致的 问题1:无法使用IPv6 问题2:无论是启动Emacs GUI还是在命令行中执行emacs -nw指令,打开Emacs的时间很长,且提示"sudo: unable to resolve host ###: Connection timed out" 问题3:打开/etc/hosts时提示文件正在被使用无法显示文件内容 解决方法:在/etc/hosts中,增加一行"127.0.1.1 ###"

JSON方式提交文档时SOLR报:AtomicUpdateDocumentMerger Unknown operation for the an atomic update, operation ignored

文档是数组转成的json 原数组: array( 0 =>3, 1 =>3, 2 =>4, 3 =>5, 4 =>5, 5 =>6) 用array_unique去掉数组中重复的元素后,插入时报错. 原因: array_unique去重之后,原数组的下标被保留了.数组为 array( 0 =>3, 2 =>4, 3 =>5, 5 =>6 ) 在json_encode数组时,会把下标不连续的数组解析成json字符串例如{"0":&

TNS-12535: TNS:operation timed out以及TNS-00505: Operation timed out的处理

序言:查看alert日志,发现很多报错信息:[[email protected] trace]$ more alert_powerdes.log *********************************************************************** *********************************************************************** Fatal NI connect error 12170. VER

TNS-12535: TNS:operation timed out案例解析

一数据库突然连接不上,在自己电脑上使用SQL Developer也连接不上.立即使用SecureCRT连接上了这台服务器,从下面几个方面检查. 1:检查了数据库的状态是否正常 $ sqlplus / as sysdba   SQL*Plus: Release 10.2.0.5.0 - Production on Mon May 16 11:07:55 2016   Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.     Connec

TNS-12502: TNS:listener received no CONNECT_DATA from client

检查我们的一台ORACLE数据库的监听日志发现有不少TNS-12502错误信息.如下所示 TNS-12502: TNS:listener received no CONNECT_DATA from client   09-DEC-2014 15:47:06 * (CONNECT_DATA=(SERVICE_NAME=epps)(CID=(PROGRAM=D:\Tasks\FGIS2MES\CEG\gmt_auto.exe)(HOST=CEGWEB1)(USER=cegadmin))) * (AD

TNS-12560: TNS: 协议适配器错误

Microsoft Windows [版本 5.2.3790] (C) 版权所有 1985-2003 Microsoft Corp. C:\Documents and Settings\user1>lsnrctl LSNRCTL for 32-bit Windows: Version 9.2.0.7.0 - Production on 27-8月 -2008 09:33 :43 Copyright (c) 1991, 2002, Oracle Corporation. All rights re

ORACLE11g ORA-12514: TNS: 监听程序当前无法识别连接描述符中请求的服务

1.TNS连接错误 同事跟我说连接oracle数据库报错ORA-12514: TNS: 监听程序当前无法识别连接描述符中请求的服务,如下所示: 2.查看本地TNSPING 查看本地的tns配置: WXX = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.121.58)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl) ) ) 查看本

oracle数据库tns配置方法详解

TNS简要介绍与应用 Oracle中TNS的完整定义:transparence Network Substrate透明网络底层,监听服务是它重要的一部分,不是全部,不要把TNS当作只是监听器. TNS是Oracle Net的一部分,专门用来管理和配置Oracle数据库和客户端连接的一个工具,在大多数情况下客户端和数据库要通讯,必须配置TNS,当然在少数情况下,不用配置TNS也可以连接Oracle数据库,比如通过JDBC.如果通过TNS连接Oracle,那么客户端必须安装Oracle client