点击打开链接

2013-05-26      0个评论    来源：李志强的博客  

收藏    我要投稿

ORA-3136错误解决

1.参数含义：

SQLNET.INBOUND_CONNECT_TIMEOUT is set to a value in seconds and determines how long a client has to

provide the necessary authentication information to a database.

INBOUND_CONNECT_TIMEOUT_listenername is set to a value in seconds and determines how long a client has

to complete its connect request to the listener after the network connection has been established.

2.参数意义：

在oracle 10.2以后的版本当中将SQLNET.INBOUND_CONNECT_TIMEOUT 和 INBOUND_CONNECT_TIMEOUT_listenername参

数设置缺省为60s，之前的版本当中默认为0（即关闭此功能）。这两个参数用于防止恶意client通过网络攻击db

server

Note: This timeout restriction was introduced to combat Denial of Service (DoS) attack whereby

malicious clients attempt to flood database servers with connect requests that consumes resources.

3.报出此warning的原因如下：

a.server收到一个从恶意client发来的连接请求，在这种情况下抛出的错误将是预期的和可取的。（客户端反复输错

username/password）

b.服务器接收到一个有效的客户端连接请求,但客户需要很长时间来验证超过默认60秒。（客户端网络延迟）

c.DB服务器负载很高导致它无法在指定时间内完成客户端登录请求。（数据库服务器高负载）

4.解决办法：

a.验证db server端，本地连接是否成功（listener是否可用）

b.验证本地连接是否延迟（本地网络是否高效可用）

c.验证数据库性能（db server是否高负载）

d.告警日志是否在之前报过ORA-600或ORA-7445

e.检查是否有client反复尝试登录密码（这是目前最有可能的原因）

f.关闭此功能（将2参数设置为0，设置方法参照步骤5）也可将2参数设置为适当值。

5.修改这两个参数的方法如下：

Edit the server side sqlnet.ora file and add this parameter:

SQLNET.INBOUND_CONNECT_TIMEOUT=<n>  Where <n> is the value in seconds.

E.g.:

SQLNET.INBOUND_CONNECT_TIMEOUT = 120

Edit the listener.ora file and add this parameter:

INBOUND_CONNECT_TIMEOUT_<listenername> = <n>  Again, where <n> is the timeout value in seconds.

For example if the listener name is LISTENER then use:

INBOUND_CONNECT_TIMEOUT_LISTENER = 110

6.总结：

此warning提示，极有可能是有客户端在不知道密码的情况下，反复尝试连接数据库或登录延迟导致，个人认为可以

忽略，重启监听并不会解决该问题，只是暂时清空了监听的告警信息，也可观察一段时间，或抓取性能分析报告，确

认是否为负载过高导致性能下降从而引起的告警。

:ORA-3136 错误解决

:ORA-3136 错误解决

1、首先通过后台alter日志发现报如下错误:

Mon May 20 12:44:19 2013

WARNING: inbound connection timed out (ORA-3136)

Mon May 20 12:44:19 2013

WARNING: inbound connection timed out (ORA-3136)

Mon May 20 12:44:19 2013

WARNING: inbound connection timed out (ORA-3136)

2、观察sqlnet.log中记录如下错误:

Fatal NI connect error 12514, connecting to:

(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=XXXXX)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)

(SERVICE_NAME=XXXXXXXX)(INSTANCE_NAME=XXXX)(CID=(PROGRAM=XXXXXX)(HOST=XXXXXX)

(USER=oracle))))

VERSION INFORMATION:

TNS for Linux: Version 10.2.0.1.0 - Production

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

Time: 28-11月-2008 14:10:42

Tracing not turned on.

Tns error struct:

ns main err code: 12564

TNS-12564: TNS:connection refused

ns secondary err code: 0

nt main err code: 0

nt secondary err code: 0

nt OS err code: 0

3、重新reload一下Listner:

[oracle@XXX ~]$ lsnrctl

LSNRCTL for Linux: Version 10.2.0.4.0 - Production on 20-5月 -2013 12:54:56

Copyright (c) 1991, 2007, Oracle.  All rights reserved.

Welcome to LSNRCTL, type "help" for information.

LSNRCTL> reload

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))

The command completed successfully

LSNRCTL> services

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))

Services Summary...

Service "+ASM" has 1 instance(s).

Instance "+ASM2", status BLOCKED, has 1 handler(s) for this service...

Handler(s):

"DEDICATED" established:0 refused:0 state:ready

LOCAL SERVER

Service "+ASM_XPT" has 1 instance(s).

Instance "+ASM2", status BLOCKED, has 1 handler(s) for this service...

Handler(s):

"DEDICATED" established:0 refused:0 state:ready

LOCAL SERVER

Service "PLSExtProc" has 1 instance(s).

Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...

Handler(s):

"DEDICATED" established:0 refused:0

LOCAL SERVER

Service "XXXXXXXX" has 2 instance(s).

Instance "XXXXXX", status READY, has 1 handler(s) for this service...

Handler(s):

"DEDICATED" established:16 refused:0 state:ready

REMOTE SERVER

(ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXXXX)(PORT=1521))

Instance "XXXXXX", status READY, has 2 handler(s) for this service...

Handler(s):

"DEDICATED" established:0 refused:0 state:ready

REMOTE SERVER

(ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXX)(PORT=1521))

"DEDICATED" established:31 refused:0 state:ready

LOCAL SERVER

Service "XXXXXXXXX" has 2 instance(s).

Instance "XXXXXX", status READY, has 1 handler(s) for this service...

Handler(s):

"D000" established:0 refused:0 current:0 max:972 state:ready

DISPATCHER <machine: XXXXXXX, pid: 28579>

(ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXX)(PORT=6661))

Instance "XXXXXX", status READY, has 1 handler(s) for this service...

Handler(s):

"D000" established:0 refused:0 current:0 max:1022 state:ready

DISPATCHER <machine: XXXX, pid: 28800>

(ADDRESS=(PROTOCOL=tcp)(HOST=XXXXX)(PORT=51924))

Service "XXXXXXXX" has 2 instance(s).

Instance "XXXXXXX", status READY, has 1 handler(s) for this service...

Handler(s):

"DEDICATED" established:16 refused:0 state:ready

REMOTE SERVER

(ADDRESS=(PROTOCOL=tcp)(HOST=XXXXX)(PORT=1521))

Instance "XXXXXXX", status READY, has 2 handler(s) for this service...

Handler(s):

"DEDICATED" established:0 refused:0 state:ready

REMOTE SERVER

(ADDRESS=(PROTOCOL=tcp)(HOST=XXXXXXX)(PORT=1521))

"DEDICATED" established:31 refused:0 state:ready

LOCAL SERVER

The command completed successfully

LSNRCTL> show inbound_connect_timeout

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))

LISTENER parameter "inbound_connect_timeout" set to 60

The command completed successfully

4、修改之后观察一段时间系统恢复正常。
 

ORA-3136错误解决相关推荐

1. oracle错误01653,oracle 10g 错误 ORA 01653 的解决过程

   oracle 10g 错误 ORA 01653 的解决过程 早上用户反应在操作用友NC时报错 ORA-01653 ,详细信息:ORA-01653: 表 NCV35.GL_DETAIL 无法通过 102 ...

2. oracle错误ORA 01031,ORA-01031: insufficient privileges错误解决方法

   ORA-01031: insufficient privileges错误解决方法 今天测试一下新功能.10g的. 通过一个linux客户端访问一个linux下的orace 10g数据库. 服务器:19 ...

3. oracle ora-3136,ORA-3136 错误解决 .

   参考metalink的文档:Doc ID: Note:3136.1 and 465043.1 WARNING: inbound connection timed out (ORA-3136) 1.参数 ...

4. oracle ora 3136,oracle中ORA-3136,ORA-609

   本文章详细的介绍了关于oracle中ORA-3136,ORA-609方法,有需要的朋友可以参考一下本文章哦. 本文章详细的介绍了关于oracle中ORA-3136,ORA-609方法,有需要的朋友可以 ...

5. Oracle 数据库 Database Express Edition 11g Release 2 (11.2) 错误解决集锦（安装方面）

   前言:第一次接触数据库,想下载个oracle试玩下(虽然听说一般大企业才用),到 官网下载 了个简易版 XE 版本,安装时要注意记住自己输入的数据库密码(口令)  还有安装路径不能含有空格(Do no ...

6. 掉电引起的ORA-1172错误解决过程（二）

   由于UPS故障,导致机房连续多次掉电,问题解决后,发现一台本地测试数据库打开时报错,ORA-1172.ORA-1151错误. 掉电引起的ORA-1172错误解决过程(一):http://yangtin ...

7. PLSQL安装配置与错误解决

   最近要使用oracle数据库,Navicat固然好用,但同事都推荐PLSQL??于是下载安装连接了一波,中间各种配置的坑啊,记录一下 下载 PLSQL下载:可前往官网下载,也可在下边网址下啦~ htt ...

8. ORA-12520错误解决方法

   ORA-12520错误解决方法 参见: oracle查看允许的最大连接数和当前连接数等信息 两个参数间的关系:sessions=1.1*processes+5 c3p0hibernate ORA-12 ...

9. ORA-12560: TNS: 协议适配器错误 解决方法

   前言 我在控制台重启oracle服务端监听lsnrctl start的时候     报错:ORA-12560: TNS: 协议适配器错误 解决方法 一:检查监听口是否开启.在开始-运行,输入servi ...

最新文章

1. HDU 1506 Largest Rectangle in a Histogram
2. CF 546E(最大流
3. python创建线程
4. python 小甲鱼 好不好_[Python]小甲鱼Python视频第025课(字典：当索引不好用时)课后题及参考解答...
5. MYSQL从节点延迟问题原因及解决
6. yii2设置默认控制器
7. Educational Codeforces Round 76 (Rated for Div. 2) E. The Contest 思维 + 差分
8. Python(37)_字典嵌套
9. jQuery中bind，live，delegate与one方法的用法及区别
10. Java数学工具类MathUtil
11. 我的idea突然没有SVN了是怎么回事
12. JavaWeb之Servlet：Cookie 和 Session
13. 营业执照号码生成规则
14. Linux下OpenCV摄像头录像（c++）
15. vivo Z1的USB调试模式在哪里，打开vivo Z1USB调试模式的经验
16. Robotframework之下拉列表select
17. 花老湿学习OpenCV：Shi-Tomasi角点检测
18. 半闲居士 RGB-D slam代码编译总结
19. 认知升级三部曲（深度好文）
20. Python如何进行语法检查

热门文章

1. android 获取SD、ROM容量
2. 一文带你走进CI/CD
3. srsLTE系统安装教程
4. mac调整启动台图标
5. Linux使用445端口,利用enum4linux 445端口+wordpress插件任意文件上传的一次渗透
6. Ubuntu死机卡死问题
7. python中将数字转换为字符串
8. 徐州地区地理生物计算机考试试题,2020年初中学业水平考试 地理、生物7月14日开考...
9. Stm32 SRAM 启动方法
10. 2021-10-27 基于电影数据库的简单查询（数据库第二次实验）