Information in this document applies to any platform.
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.
ORA-609意味着不能通过监听把它附加到即将到来的连接上,因此服务器进程被终止(关闭)
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.
客户端连接有6个步骤:
- 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
鉴于以上的错误,在第3步与第4步之间时, 客户端连接就关闭了 ,此时当专有进程尝试与客户端连接时,发现连接已经关闭了
To determine the client which hit this problem we can try to match the timestamp of the error from alert log with an entry in listener.log, but this might be difficult in case of a loaded listener with many incoming connections per second.
Server sqlnet trace will not provide any information about the client.
去确定碰到问题的client,我们可以尝试去匹配alert日志中错误发生的时间戳并且在监听日志中也有相应的条目,但当 加载的监听 每秒有许多连接的时候是非常困难去判断的,服务器sqlnet的trace不会提供任何该客户端的信息
We can enable sqlnet server trace to catch the error (the match is done based on the ospid found in sqlnet server trace file name and the line with ORA-609 error):
nscon: recving a packet
nsprecv: entry
nsprecv: reading from transport...
nttrd: entry
nttrd: exit
ntt2err: entry
ntt2err: Read unexpected EOF ERROR on 15 <<<<<<< error
ntt2err: exit
nsprecv: error exit
nserror: entry
nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
nscon: error exit
nsdo: nsctxrnk=0
nsdo: error exit
nsinh_hoff: error recving request
Several possible situations can cause this to happen:
- client changed its mind and closed the connection immediately after initiating it
- client crashed
- firewall kills the connection
- some oracle timeout set on client
解决方案:
Because the entry from listener.log contains only CONNECT_DATA and CID related information we need to check the client configuration for any sqlnet timeouts:
- possible timeouts in sqlnet.ora in client oracle home:
sqlnet.outbound_connect_time
sqlnet.recv_timeout
sqlnet.send_timeout
tcp_connect_timeout
检查客户端目录中sqlnet.ora的超时设置,通常是这个引起的
- possible timeout in client connect descriptor (hardcoded in client application or in client tnsnames.ora):
connect_timeout