ITPub博客

首页 > 数据库 > 数据库开发技术 > TNS-12535 TNS-00505的处理方法

TNS-12535 TNS-00505的处理方法

数据库开发技术 作者:ericwen2015 时间:2016-02-15 11:10:28 0 删除 编辑

硬件说明:

操作系统版本:ORACLE LINUX 6.3  64位

数据库版本:11.2.0.3   64位

 

问题说明:

在检查数据库的alert日志的时候,发现大量的12170和TNS-12535的错误;

Fatal NI connect error 12170.

 

  VERSION INFORMATION:

    TNS for Linux: Version 11.2.0.3.0 - Production

    Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production

    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production

  Time: 06-APR-2014 10:46:14

  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=110.80.1.83)(PORT=50226))

Sun Apr 06 10:46:24 2014

 

问题解决:

在metalink平台上面查找,该症状和文档 ID (1628949.1)描述的症状完全一样,根据文档的内容整理如下:

1、出现问题的版本

Oracle Net Services - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1]Information in this document applies to any platform.

 

2、出现错误的症状或报错格式如下:

Fatal NI connect error 12170.VERSION INFORMATION:TNS for 64-bit Windows: Version 11.2.0.3.0 - ProductionOracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - ProductionWindows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - ProductionTime: 22-FEB-2014 12:45:09Tracing not turned on.Tns error struct:ns main err code: 12535TNS-12535: TNS:operation timed outns secondary err code: 12560nt main err code: 505TNS-00505: Operation timed outnt secondary err code: 60nt OS err code: 0***Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=121.23.142.141)(PORT=45679))

The PORT field here is the ephemeral port assigned to the client for this connection. This does not correspond to the listener port.

 

3、问题的原因

The alert.log message indicates that a connection was terminated AFTER it was established to the instance. In this case, it was terminated 2 hours and 3 minutes after the listener handed the connection to the database.

This would indicate an issue with a firewall where a maximum idle time setting is in place.

The connection would not necessarily be "idle". This issue can arise during a long running query or when using JDBC Thin connection pooling. If there is no data 'on the wire' for lengthy

periods of time for any reason, the firewall might terminate the connection.

4、解决方法:

The following parameter, set at the **RDBMS_HOME/network/admin/sqlnet.ora, can resolve this kind of problem. DCD or SQLNET.EXPIRE_TIME can mimic data transmission between the server and the client during long periods of idle time. SQLNET.EXPIRE_TIME=n Where <n> is a non-zero value set in minutes. 

进入ORACLE_HOME/network/admin目录下,添加sqlnet.ora文件,增加一行SQLNET.EXPIRE_TIME=10

 

5、补充说明SQLNET.EXPIRE_TIME

Purpose

To specify a time interval, in minutes, to send a check to verify that client/server connections are active. The following usage notes apply to this parameter:

 

6、做完以上操作后,重启数据库的监听;

 

 

详细的metalink链接 :https://support.oracle.com/epmos/faces/DocumentDisplay?id=1628949.1

-----------------------------------------------------------------------------------------------------

ORACLE 数据库运维群  367875324

------------------------------------------------------------------------------------------------------

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/30373825/viewspace-1988904/,如需转载,请注明出处,否则将追究法律责任。

上一篇: 没有了~
请登录后发表评论 登录
全部评论

注册时间:2015-07-26

  • 博文量
    41
  • 访问量
    24282