ORA-27504,ORA-27300,ORA-27301,ORA-27302,ORA-27303

Oracle 10.2.0.4 (64bit)  , Linux AS 5.3  64 bit  , 4节点RAC系统

 

节点 1, 2, 3 用于生产系统 , alert log 基本正常 。

节点 4  用于报表查询系统 ,  alert log 中有报错信息,发生问题时候节点4的负载较高,但是也不是最高。 

 

备注:  这里通过将节点 4 上的remote_listener置为空,将1,2,3 和 节点4 分开,不存在连接1,2,3的session

连接到节点4 的情况, 同样节点4上的session 也不会因为负载连接到其他用于生产系统的节点 。


节点1  上的alert log  :  

 

Tue Oct  5 10:05:59 2010
Thread 1 advanced to log sequence 23897 (LGWR switch)
  Current log# 31 seq# 23897 mem# 0: /ocfs_ctrl_redo/mxdell/redo31_a.log
  Current log# 31 seq# 23897 mem# 1: /ocfs_data/mxdell/redo31_b.log
Tue Oct  5 10:17:45 2010
Trace dumping is performing id=[cdmp_20101005101745]
Tue Oct  5 10:36:00 2010
Thread 1 advanced to log sequence 23898 (LGWR switch)
  Current log# 32 seq# 23898 mem# 0: /ocfs_ctrl_redo/mxdell/redo32_a.log
  Current log# 32 seq# 23898 mem# 1: /ocfs_data/mxdell/redo32_b.log

 

 


节点2  上的alert log  :  

 

Tue Oct  5 10:17:42 2010
Thread 3 advanced to log sequence 23412 (LGWR switch)
  Current log# 40 seq# 23412 mem# 0: /ocfs_ctrl_redo/mxdell/redo40_a.log
  Current log# 40 seq# 23412 mem# 1: /ocfs_data/mxdell/redo40_b.log
Tue Oct  5 10:17:45 2010
Trace dumping is performing id=[cdmp_20101005101745]
Tue Oct  5 10:40:22 2010
Thread 3 advanced to log sequence 23413 (LGWR switch)
  Current log# 41 seq# 23413 mem# 0: /ocfs_ctrl_redo/mxdell/redo41_a.log
  Current log# 41 seq# 23413 mem# 1: /ocfs_data/mxdell/redo41_b.log

 

 

 

 

节点4 上的alert log :

 

Tue Oct  5 10:17:30 2010
Thread 4 advanced to log sequence 16150 (LGWR switch)
  Current log# 48 seq# 16150 mem# 0: /ocfs_ctrl_redo/mxdell/redo48_a.log
  Current log# 48 seq# 16150 mem# 1: /ocfs_data/mxdell/redo48_b.log
Tue Oct  5 10:17:44 2010
Errors in file /u01/product/admin/mxdell/udump/mxdell4_ora_375.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:sskgxp_select failed with status: 3
ORA-27301: OS failure message: No such process
ORA-27302: failure occurred at: skgxpvfymmtu
ORA-27303: additional information: MTU could not be verified.  Did not receive valid message.
Tue Oct  5 10:17:45 2010
Trace dumping is performing id=[cdmp_20101005101745]

Tue Oct  5 10:47:30 2010
Thread 4 advanced to log sequence 16151 (LGWR switch)
  Current log# 43 seq# 16151 mem# 0: /ocfs_ctrl_redo/mxdell/redo43_a.log
  Current log# 43 seq# 16151 mem# 1: /ocfs_data/mxdell/redo43_b.log
Tue Oct  5 11:17:30 2010
Thread 4 advanced to log sequence 16152 (LGWR switch)
  Current log# 44 seq# 16152 mem# 0: /ocfs_ctrl_redo/mxdell/redo44_a.log
  Current log# 44 seq# 16152 mem# 1: /ocfs_data/mxdell/redo44_b.log

 

 

 

 

节点4上的trace 文件 (截断) : 

 

/u01/product/admin/mxdell/udump/mxdell4_ora_375.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/product/oracle
System name:    Linux
Node name:      mxrac04
Release:        2.6.18-128.el5
Version:        #1 SMP Wed Dec 17 11:41:38 EST 2008
Machine:        x86_64
Instance name: mxdell4
Redo thread mounted by this instance: 4
Oracle process number: 0
Unix process pid: 375, image: oracle@mxrac04

SKGXPVFYMMTU: select failed 3.
*** 2010-10-05 10:17:44.470
SKGXPVFYMMTU: Could not create context which satisfies the minimum
              MTU requirement of 32768 bytes
struct ksxpp * ksxppg_ [0x68a7b38, 0x1a307610) = 0x1a307608
Dump of memory from 0x000000001A307608 to 0x000000001A308750
01A307600                   1A309680 00000000          [..0.....]
01A307610 1A30AC20 00000000 00000000 00000000  [ .0.............]
01A307620 00000000 00000000 00000000 00000000  [................]
        Repeat 269 times
01A308700 00000000 00000000 96F9AFAA 0000012C  [............,...]
01A308710 00000000 00000000 00000000 00000000  [................]
  Repeat 3 times
struct skgxpctx * ksxp_osdctx [0x1a307608, 0x1a309688) = 0x1a309680
Dump of memory from 0x000000001A309680 to 0x000000001A30AC20
01A309680 00000000 00000000 00000000 00000000  [................]
01A309690 052FC280 00000000 068966E0 00000000  [../......f......]
01A3096A0 00000000 00000000 00000000 00000000  [................]
01A3096B0 A0EEAA04 00002B07 000000DA 00000000  [.....+..........]
01A3096C0 A0EEAA14 00002B07 000000DB 00000000  [.....+..........]
01A3096D0 A0EEAA2C 00002B07 000000DC 00000000  [,....+..........]
01A3096E0 A0EEAA48 00002B07 000000DD 00000000  [H....+..........]
01A3096F0 A0EEAA68 00002B07 000000DE 00000000  [h....+..........]
01A309700 A0EEAA88 00002B07 000000DF 00000000  [.....+..........]
01A309710 A0EEAAB0 00002B07 000000E3 00000000  [.....+..........]
01A309720 A0EEAADC 00002B07 000000E4 00000000  [.....+..........]
01A309730 A0EEAAF0 00002B07 00000000 00000000  [.....+..........]
01A309740 A0EEAB08 00002B07 00000000 00000000  [.....+..........]
01A309750 000005DC 00000000 00000001 00000001  [................]
01A309760 31687465 00000000 00000000 00000000  [eth1............]
01A309770 00000000 00000000 00000000 00000000  [................]
        Repeat 14 times
01A309860 0E01A8C0 00000000 00000000 00000000  [................]
01A309870 00000000 00000000 00000000 00000000  [................]
        Repeat 153 times
01A30A210 00000000 00000000 00010006 000005DC  [................]
01A30A220 00000000 000003E8 000003E8 00000000  [................]
01A30A230 0000003C 00000005 00000400 0000012C  [<...........>01A30A240 1A30B720 00000000 1A30B720 00000000  [ .0..... .0.....]
01A30A250 00000400 00000001 00000000 00000000  [................]
01A30A260 00000000 00000000 00000000 00000000  [................]
        Repeat 1 times
01A30A280 4CAB4F9D 00000000 0007244B 00000000  [.O.L....K$......]
01A30A290 00000000 00000000 00000064 00000000  [........d.......]
01A30A2A0 00000000 00000000 00000000 00000000  [................]
        Repeat 3 times
01A30A2E0 00000000 00000000 1A30A2E8 00000000  [..........0.....]
01A30A2F0 1A30A2E8 00000000 1A30A2F8 00000000  [..0.......0.....]
01A30A300 1A30A2F8 00000000 1A30A308 00000000  [..0.......0.....]
01A30A310 1A30A308 00000000 1A30A318 00000000  [..0.......0.....]
01A30A320 1A30A318 00000000 1A30A328 00000000  [..0.....(.0.....]
01A30A330 1A30A328 00000000 1A30A338 00000000  [(.0.....8.0.....]
01A30A340 1A30A338 00000000 00000010 00000000  [8.0.............]
01A30A350 00000000 00000000 00000000 00000000  [................]
        Repeat 19 times
01A30A490 00000000 00000000 1A30A498 00000000  [..........0.....]
01A30A4A0 1A30A498 00000000 00000000 7A9F91A8  [..0............z]
01A30A4B0 00000000 00000007 00000000 A4080002  [................]
01A30A4C0 0E01A8C0 00000000 00000000 0E01A8C0  [................]
01A30A4D0 0000A408 00000000 00000000 00000000  [................]
01A30A4E0 00000000 00000000 00000000 00000000  [................]
  Repeat 115 times
kgefec: fatal error 0
*** 2010-10-05 10:17:44.471
ksedmp: internal or fatal error
ORA-00603: ORACLE server session terminated by fatal error
ORA-27504: IPC error creating OSD context
ORA-27300: OS system dependent operation:sskgxp_select failed with status: 3
ORA-27301: OS failure message: No such process
ORA-27302: failure occurred at: skgxpvfymmtu
ORA-27303: additional information: MTU could not be verified.  Did not receive valid message.
Current SQL information unavailable - no session.
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst()+31          call     ksedst1()            000000000 ? 000000001 ?
                                                   7FFF09BE0000 ? 7FFF09BE0060 ?
                                                   7FFF09BDFFA0 ? 000000000 ?
ksedmp()+610         call     ksedst()             000000000 ? 000000001 ?
                                                   7FFF09BE0000 ? 7FFF09BE0060 ?
                                                   7FFF09BDFFA0 ? 000000000 ?
ksfdmp()+21          call     ksedmp()             000000003 ? 000000001 ?
                                                   7FFF09BE0000 ? 7FFF09BE0060 ? 

 

 

查询Metalink 发现是Bug :

 

Bug 7331323 - ORA-27302 "failure occurred at: skgxpvfymmtu" in RAC [ID 7331323.8] 

 修改时间 17-AUG-2010     类型 PATCH     状态 PUBLISHED 
function getdoc2(docstr,mlstr) { pos=docstr.indexOf(':'); docid=docstr.substring(pos+1,docstr.length); tgt="_self"; if ( location.href.slice(7,12) == "webiv" || location.href.slice(7,11) == "rmsu" ) { loc="Get?WwwID=note:" + docid; } else { if ( location.href.slice(7,12) == "metal" || location.href.slice(7,12) == "suppo" ) { loc=mlstr + docid; } else { loc="http://metalink.oracle.com/metalink/plsql/"+mlstr+docid; } } window.open(loc,tgt); return; } function getdoc(docstr) { getdoc2(docstr,"showdoc?db=NOT&id="); }

Bug 7331323  ORA-27302 "failure occurred at: skgxpvfymmtu" in RAC

 This note gives a brief overview bug 7331323.
 The content was last updated on: 17-AUG-2010
 Click here for details of each of the sections below.
 This bug is marked as an important issue.
 There are additional notes on this bug in Note:746888.1

Affects:

Product (Component)Oracle Server (Rdbms)
Range of versions believed to be affectedVersions >= 10.2.0.4
Versions confirmed as being affected
  • 11.1.0.6
  • 10.2.0.4
Platforms affectedGeneric (all / most platforms affected)

 It is believed to be a regression in default behaviour thus:
   Regression introduced in 10.2.0.4
   Regression introduced in 11.1.0.6

Fixed:

This issue is fixed in
  • 10.2.0.5 (Server Patch Set)

Symptoms:

Related To:

  • Error May Occur
  • ORA-27302
  • RAC (Real Application Clusters) / OPS

Description

This problem is introduced in 10.2.0.4 and 11.1.0.6.
 
In a RAC environment errors of the form. below may 
be seen causing process failures:
 
 ORA-00603: ORACLE server session terminated by fatal error
 ORA-27504: IPC error creating OSD context
 ORA-27300: OS system dependent operation:sskgxp_select failed with status: 3
 ORA-27301: OS failure message: No such process
 ORA-27302: failure occurred at: skgxpvfymmtu
 ORA-27303: additional information: MTU could not be verified. Did not receive valid message.
 
See Note:746888.1 for more details.
 
HOOKS PSE:A204 ERROR:ORA-27302 SPIN:sskgxp_select LIKELYAFFECTS XAFFECTS_10.2.0.4 XAFFECTS_V10020004 AFFECTS=10.2.0.4 XAFFECTS_11.1.0.6 XAFFECTS_V11010006 AFFECTS=11.1.0.6 XAFFECTS_11.1.0.7 XAFFECTS_V11010007 AFFECTS=11.1.0.7 XPRODID_5 PRODUCT_ID=5 PRODID-5 RDBMS XCOMP_RDBMS COMPONENT=RDBMS TAG_ERROR TAG_OPS TAG_RA204 TAG_RB106 TAG_REGRESSION ERROR OPS RA204 RB106 REGRESSION FIXED_10.2.0.5

Further details on this issue can be found in Note:746888.1

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice.

References

Bug:7331323 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

 

 

 

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

转载于:http://blog.itpub.net/35489/viewspace-675480/

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.4 to 11.1.0.6 Information in this document applies to any platform. Description The following errors may be reported: ORA-00603: ORACLE server session terminated by fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:sskgxp_select failed with status: 3 ORA-27301: OS failure message: No such process ORA-27302: failure occurred at: skgxpvfymmtu ORA-27303: additional information: MTU could not be verified. Did not receive valid message. These errors are caused by more aggressive checking introduced in 10.2.0.4. Likelihood of Occurrence This only affects Oracle Real Application Clusters and can be reported in ASM as well as database instances. The issue was introduced in Oracle 10.2.0.4 so earlier versions are not affected Possible Symptoms The errors above can be reported by Oracle shadow processes or by background processes. Additionally they may be reported in the alert.log. The symptoms can include: - process failure - startup failure - processes spinning in function sskgxp_select with high CPU usage Workaround or Resolution There is no workaround available. However, if the instance fails to start, a reboot of the server supporting the instance will usually allow startup to succeed. Patches At the time of writing, patches were under development on top of 10.2.0.4 on some platforms. Please check Patch 7331323 for availability on your platform. The problem is resolved in 11.1.0.7. References NOTE:419937.1 - Alert.log shows frequently "skgxpvfymmtu: process failed because of a resource problem in the OS" NOTE:419871.1 - Failures due to "skgxpvfymmtu: process failed because of a resource problem in the OS" on 32-bit Linux

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值