NS Primary Error: TNS-12547: TNS: 丢失连接

上一篇 / 下一篇  2008-07-22 18:25:00 / 个人分类:oracle管理

Shared方式连接oracle 10R2:

 

Trace文件中:

*** 2008-07-21 09:26:51.381

async error encountered when answering new connection:

  NS Primary Error: TNS-12547: TNS:丢失连接

  NS Secondary Error: TNS-12560: TNS:协议适配器错误

  NT Generic Error: TNS-00517:丢失连接

  64-bit Windows Error: 54: Unknown error

 

 

找到一个相关文档,还没有按照文档去尝试或者打补丁(没有验证),先记录下:

 

Subject:ORA-7445 Core Dump In nsclose or nsevidh_GetIPC
 Doc ID:Note:555512.1Type:PROBLEM
 Last Revision Date:27-FEB-2008Status:MODERATED

In this Document
  Symptoms
  Cause
  Solution
  References


@ (AuthWiz 2.5.3) Created fromSR 18544138.6
@Click here to edit in wizard.  

This document is being delivered to you via Oracle Support'sRapid Visibility(RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2
This problem can occur on any platform.
Applies to:

Symptoms

o Alert log shows core dump in function QSMPSUMP or QSMPPTDE:

ORA-07445: exception encountered: core dump [nsclose()+132]
ORA-07445: exception encountered: core dump [NSEVIDH_GETIPC()+448]

o Trace file can show following TNS errors:


NS Primary Error: TNS-12535: TNS:operation timed out
NS Secondary Error: TNS-12606: TNS: Application timeout occurred


o Stack trace is similar to:


ksedmp funlockfile nsclose nsevidh nsevrec
nsevwait ksnwait kslwaitns_timed kskthbwt kslwait

-- OR --

nsevidh_GetIPC nsevrec nsevwait ksnwait ksliwat
kslwaitctx kslwait kmdmai kmmrdp

Cause

This is internal Net Bug 6784671
Abstract: IPV6JAVANET:ORA-7445: [NSEVIDH_GETIPC()+448] [ACCESS_VIOLATION][ADDR:0XF0E0D14

Crash in nsevidh_GetIPC or nsevidh along with timeout errors in dispatcher trace.

Solution

The bug 6784671 is fixed in Oracle release 11.1.

A possible workaround is to increase the inbound_connect_timeout as shown below:

1. In server side sqlnet.ora file add

SQLNET.INBOUND_CONNECT_TIMEOUT

For e.g
SQLNET.INBOUND_CONNECT_TIMEOUT = 100

2. In listener.ora file -

INBOUND_CONNECT_TIMEOUT_<listenername> = 100

For e.g if the listener name is LISTENER then -
INBOUND_CONNECT_TIMEOUT_LISTENER = 100


Once you set the parameter and restart the listener, you will be able to issue
the following lsnrctl command:

LSNRCTL>show inbound_connect_timeout

You can also set this dynamically and then save_config:

LSNRCTL>set inbound_connect_timeout 100
LSNRCTL>save_config


One-off patches may be available depending on your current release and operating system.
To obtain a patch from MetaLink:
1) Click on Patches.
2) Click on Simple Search
3) Enter patch number: 6784671
4) Select your O/S
5) Click Go.

References

@Bug 6817825- ORA-7445[NSCLOSE()+161] AND ORA-7445[NSEVIDH()+1530]
@Bug 6784671- IPV6JAVANET:ORA-07445: [NSEVIDH_GETIPC()+448] [ACCESS_VIOLATION][ADDR:0XF0E0D14
Note 465043.1- Troubleshooting ORA - 3136 WARNING Inbound Connection Timed Out



Help us improve our service. Pleaseemailus your comments for this document..


TAG:

 

评分:0

我来说两句

显示全部

:loveliness: :handshake :victory: :funk: :time: :kiss: :call: :hug: :lol :'( :Q :L ;P :$ :P :o :@ :D :( :)

日历

« 2008-10-08  
   1234
567891011
12131415161718
19202122232425
262728293031 

数据统计

  • 访问量: 11431
  • 日志数: 1532
  • 建立时间: 2008-04-17
  • 更新时间: 2008-10-07

RSS订阅

Open Toolbar