1 问题
数据库在巡检的时候发现alert日志里出现监听相关的报错
- rac1
Tue Sep 03 10:19:48 2019
***********************************************************************
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: 03-SEP-2019 10:19:48
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
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.201.111)(PORT=49310))
- rac2
Tue Sep 03 16:47:06 2019
***********************************************************************
Fatal NI connect error 12547, connecting to:
(LOCAL=NO)
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: 03-SEP-2019 16:47:06
Tracing not turned on.
Tns error struct:
ns main err code: 12547
TNS-12547: TNS:lost contact
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 (175308) as a result of ORA-609
数据库的ALERT日志中常会见到ORA-609
、ORA-3136
/ORA-609
、TNS-12537
and TNS-12547
or TNS-12170
、TNS-12535
等相关错误
2 原因排查与解决
2.1 RAC1的TNS-12535
、TNS-00505
错误原因
参考官方说明关于该警告的说明:
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.
可能的原因:
- 网络攻击,例如:半开连接攻击
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. - 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. - 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)
2.2 解决办法
1.查找问题时间段的alert日志和监听日志,其位置分别是$ORACLE__BASE/diag/rdbms/db_name/$ORACLE_SID/trace/
和$ORACLE__BASE/diag/tnslsnr/hostname/listener/trace/
2.如果alert日志显示如上报错,但listener日志显示正常,那么说明确实是数据库以外的问题,监听正常,就是网络方面的原因了。可能就是client暂时没有连接。
除非大批量客户端或所有的客户端都连不上,才用排查监听、网络或防火墙权限等问题。
出现这个报错,是会两个节点上都有的。
3.如果监听日志显示了其他报错,那么再根据报错找到相应的解决办法。
- 这跟监听的一个参数有关:
SQLNET.INBOUND_CONNECT_TIMEOUT
这个参数从9i开始引入,指定了客户端连接服务器并且提供认证信息的超时时间,如果超过这个时间客户端没有提供正确的认证信息,服务器会自动中止连接请求,同时会记录试图连接的IP地址和ORA-12170:TNS:Connect timeout occurred
错误。
这个参数的引入,主要是防止DoS攻击,恶意攻击者可以通过不停的开启大量连接请求,占用服务器的连接资源,使得服务器无法提供有效服务。在10.2.0.1起,该参数默认设置为60秒。
但是,这个参数的引入也导致了一些相关的Bug。比如:
该参数可以通过设置为0来禁用,在服务端: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
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,即无限制。 - 或
2.3 RAC2的ORA-609
错误原因
参考官方说明关于该警告的说明:
ORA-609 means "could not attach to incoming connection" so the database process was 'aborted' (closed) because it couldn't attach to the incoming connection passed to it by the listener.
The reason for this is found in the sqlnet error stack, in our case is:
TNS-12537: TNS:connection closed.
Basically the dedicated process didn't have a client connection anymore to work with.
此报错类似通知:ORACLE因为ORA-609关闭或者叫中止了一个到数据库的专有连接–ospid (28725)。
ORA-609错误原因是:无法与进入的连接进行联系,所以无法将此连接转入监听器,所以数据库的process中止此进程。
此时报错TNS-12537: TNS:connection closed
,根本原因为客户端连接不正常。
客户端通过监听器连接ORACLE数据库的过程:
- Client initiates a connection to the database so it connects to the listener
- Listener starts (fork) a dedicated database process that will receive this connection (session)
- After this dedicated process is started, the listener passes the connection from the client to this process
- The server process takes the connection from the listener to continue the handshake with the client
- Server process and client exchange information required for establishing a session (ASO, Two Task Common, User logon)
- Session is opened
简单说就是:
1.客户端连接到监听器
2.监听派生fork一个子进程,交转化为专有服务器进程dedicated database process
3.第2步完成后,监听将客户端的连接转入此专有进程dedicated process
4.服务器进程收到从监听来的连接信息后,需要继续与客户端的连接进行handshake
5.服务器进程与客户端进程交换建立会话需要的信息,如用户名、密码等
6.以上OK后,SESSION OPEN。
出现这个问题时,就是在介于3、4步时客户端连接关闭,dedicated database process与客户端通信时发现客户端关闭了。
生产环境遇上这个报错一般是ISIS那边发新版本,数据库监听状态正常,巡检工具能正常询价,能连上就没事
他们有时候发版本,会把web之类的重启,就会出现这种报错
如果在月报体现,就是“就说明该报错由ISIS发布版本导致的就行”(这种记录看心情)
监听正常,就是网络方面原因了
网上的解决办法就是可以不记录追踪信息,所以记录着忽略就行
除非大批量客户端或所有的客户端都连不上,才用排查监听、网络或防火墙权限等问题
出现这个报错,是会两个节点上都有的