今天做数据库巡检，发现下面两个错误几乎每天都会出现。请大家帮忙看看。数据库版本：Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
操作系统版本：HP-UX IA (64-bit) B.11.31错误一：
描述：几乎每天早上这个时间都会出现，来自同一台应用服务器。
问题：原因是连接超时了，还是应用方面的问题？
内容：
Mon Aug 01 01:36:56 2011
***********************************************************************Fatal NI connect error 12170. VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 01-AUG-2011 01:36:57
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNSperation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=198.120.1.24)(PORT=53239))Wed Aug 03 01:23:05 2011
***********************************************************************Fatal NI connect error 12170. VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 03-AUG-2011 01:23:05
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNSperation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=198.120.1.24)(PORT=53466))
WARNING: inbound connection timed out (ORA-3136)错误二：
问题：网上查到好像说是ORACLE 11g的bug Bug id 7659739，具体是什么原因会引起这个错误，另外现在是否有解决方案？
内容：
Sat Aug 06 01:30:47 2011
***********************************************************************Fatal NI connect error 12637, connecting to:
(LOCAL=NO) VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 06-AUG-2011 01:30:47
Tracing not turned on.
Tns error struct:
ns main err code: 12637
TNS-12637: Packet receive failed
ns secondary err code: 12532
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (21632_1)Sun Aug 07 01:20:15 2011
***********************************************************************Fatal NI connect error 12637, connecting to:
(LOCAL=NO) VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 07-AUG-2011 01:20:15
Tracing not turned on.
Tns error struct:
ns main err code: 12637
TNS-12637: Packet receive failed
ns secondary err code: 12532
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (4394_1)
操作系统版本：HP-UX IA (64-bit) B.11.31错误一：
描述：几乎每天早上这个时间都会出现，来自同一台应用服务器。
问题：原因是连接超时了，还是应用方面的问题？
内容：
Mon Aug 01 01:36:56 2011
***********************************************************************Fatal NI connect error 12170. VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 01-AUG-2011 01:36:57
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNSperation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=198.120.1.24)(PORT=53239))Wed Aug 03 01:23:05 2011
***********************************************************************Fatal NI connect error 12170. VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 03-AUG-2011 01:23:05
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNSperation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=198.120.1.24)(PORT=53466))
WARNING: inbound connection timed out (ORA-3136)错误二：
问题：网上查到好像说是ORACLE 11g的bug Bug id 7659739，具体是什么原因会引起这个错误，另外现在是否有解决方案？
内容：
Sat Aug 06 01:30:47 2011
***********************************************************************Fatal NI connect error 12637, connecting to:
(LOCAL=NO) VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 06-AUG-2011 01:30:47
Tracing not turned on.
Tns error struct:
ns main err code: 12637
TNS-12637: Packet receive failed
ns secondary err code: 12532
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (21632_1)Sun Aug 07 01:20:15 2011
***********************************************************************Fatal NI connect error 12637, connecting to:
(LOCAL=NO) VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.7.0 - Production
Time: 07-AUG-2011 01:20:15
Tracing not turned on.
Tns error struct:
ns main err code: 12637
TNS-12637: Packet receive failed
ns secondary err code: 12532
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
ORA-609 : opiodr aborting process unknown ospid (4394_1)
解决方案 »
- oracle两个数据库同步
- sqlplus一个奇怪的问题
- TNS: 协议适配器错误 求助!!!
- Oracle8升级到Oracle10后，SQL查询的结果排序不一致
- 一个简单的sql问题，给出正确答案的都给分啊！
- 100分求助各位高手指教："Error while trying to retrieve text for error ORA-01041”？
- 一个关于select命令的小问题？
- 为什么这么一个简单的sql语句都运行不了？！！！
- 在ORACLE数据库中SYS用户的默认口令是什么？
- ora 1007的问题求教
- mysql 查询问题
- 我想使用windows 7，同时想安装Oracle，请在windows 7上安装了Oracle的朋友帮帮忙好忙，如何才可以啊
而第二个问题，我在oracle的support网站确实查到有一个tns-12637的bug，但是网页太卡了，想看下详细信息直接页面打不开
修改时间 25-JAN-2010 类型 PROBLEM 状态 MODERATED In this Document
Symptoms
Changes
Cause
Solution
References--------------------------------------------------------------------------------Platforms: 1-914CU; This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.7
Information in this document applies to any platform.Symptoms
Connexion fails with the error : TNS-12518: TNS:listener could not hand off client connectionOne of the following errors could also appears :ORA-12547 / TNS-12547: lost contact
ORA-12537 / TNS-12537: connection closed
ORA-3135 / TNS-3135 : connection lost contact
ORA-3113 / TNS-3113 : end-of-file on communication channel
ORA-3106 / TNS-3106 : fatal two-task communication protocol error
ORA -3136 / TNS-3136 : WARNING inbound connection timed out
ORA-12535 / TNS-12535: TNS:operation timed out
ORA-12170 / TNS-12170: Connect timeout occurred
ORA-12637 / TNS-12637: Text: Packet receive failed Changes
memory consumption and/or high load
Cause
In general ORA-12518 occurs if there is a resource problem , may be on the listener side or on the Database server.It indicates a condition where the process is not able to make any more memory allocations either due to non-availability of resource or the process has reached the 32 bit (VM Size) limit
Solution
1- Timer issues causing abnormal threads :
Set the parameters SQLNET.INBOUND_CONNECT_TIMEOUT and INBOUND_CONNECT_TIMEOUT_listenername to 0 (indefinite) or to an approprate value for the application.
From Oracle base version 10.2.0.1 onwards the default value of INBOUND_CONNECT_TIMEOUT_<listenername> is 60 seconds. For previous releases it is zero by default.a) Please add following parameter in listener.ora
INBOUND_CONNECT_TIMEOUT_<listener_name> = 0For example, if the listener name is listenerTest, then:
INBOUND_CONNECT_TIMEOUT_listenerTest = 0ANDb) Add the following parameter to the sqlnet.ora file on the Database server
side:
SQLNET.INBOUND_CONNECT_TIMEOUT = 0The listener and database will need to be restarted after these changes.These parameters are set on the SERVER side:
listener.ora: INBOUND_CONNECT_TIMEOUT_listenername
sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUTNote: 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.Fore more info/setting on inbound connection time out, check the following note :
Note 465043.1 - Troubleshooting ORA - 3136 WARNING Inbound Connection Timed Out2 - Lack of available memory :
Increase memory and swap in the system3 - Less of processes in the database,:
Increase processes parameter if using dedicated connexion (init.ora / spfile file)
In unix, adjust resource limits to increase the number of max processes allowed. 4 - Set /3GB option :
Switch in the BOOT.INI file to enable the 4GB feature.
This allows a process to address 3GB and reserving 1GB for the kernel. 5- Tune SGA / shared_pool_size :
Reduce the SGA size to a reasonable figure which allows the user process to have enough memory to run.
Decrease the size of the database SGA by reducing the PGA_AGGREGATE_TARGET or SGA_MAX_SIZE or both.
The amount of memory for a session depends upon PGA_AGGREGATE_TARGET.
If PGA_AGGREGATE_TARGET is set to a very small value ,Oracle session may exceed this value.6 - Set or Tune MTS :
Configure MTS or increase the number of DISPATCHERS (if Shared Server is being used).7- If the listener crash with a core dump and the ora-12518 appears in the log, then you are probably hitting Bug 6139856 due to heavy load or out of memory.For more detail and solutions, see :
Note 549932.1 - TNS Listener Crash with Core dump