Oracle 11g alert log 新增消息 opiodr aborting process unknown ospid (1951) as a result of ORA-28 说明

原创 2012年08月04日 00:36:02

 

一.Alert log 说明

 

Oracle 11.2.0.2 的数据库中alert log发现大量如下log

 

Fatal NI connect error 12537, connectingto:

 (LOCAL=NO)

 

VERSION INFORMATION:

       TNS for HPUX: Version 11.2.0.2.0 - Production

       Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.2.0.2.0 -Production

       TCP/IP NT Protocol Adapter for HPUX: Version 11.2.0.2.0 - Production

 Time: 11-SEP-2011 17:03:56

 Tracing not turned on.

  Tnserror struct:

  nsmain err code: 12537

   

TNS-12537: TNS:connection closed

   ns secondary err code: 12560

   nt main err code: 0

   nt secondary err code: 0

   nt OS err code: 0

opiodr aborting process unknown ospid (29942) as a result of ORA-609

Sun Sep 11 17:05:23 2011

 

 

Tue Sep 13 17:56:37 2011

opiodr aborting processunknown ospid (924) as a result of ORA-28

Tue Sep 13 17:56:38 2011

opiodr aborting process unknownospid (1951) as a result of ORA-28

Tue Sep 13 17:56:40 2011

opiodr aborting process unknown ospid(1983) as a result of ORA-28

Tue Sep 13 17:56:42 2011

opiodr aborting process unknown ospid(11149) as a result of ORA-28

Tue Sep 13 17:56:43 2011

opiodr aborting process unknown ospid(17662) as a result of ORA-28

Tue Sep 13 17:58:06 2011

 

 

opidcl aborting process unknown ospid(9702) as a result of ORA-604

 

二.问题分析:

 

2.1 opiodr aborting process unknown ospid (924) as a resultof ORA-28

 

在Oracle 11.1.0.6 和 11.1.0.7 的版本中,存在一个bug:6377339。 其会在alert log 显示如下信息:

 

 ORA-28 : opiodr aborting process unknown ospid (21016_3086862016)

 

       这样的提示信息会让我们产生疑惑. 所以在Oracle 11.2 版本中对这个bug进行修复,修复之后的提示信息变成了:

opidcl abortingprocess unknown ospid (32110) as a result of ORA-28

 

opiodr aborting process信息仅仅是一个消息,它是Oracle 11g里新添加的一个消息,用来记录进程的异常退出。

该消息一般用来记录有权限的用户kill session信息。

 

 

示例:

"opiodr aborting process unknown ospid(28342) as a result of ORA-28"

解释:

"unknown" => means it is not abackground or shadow process that is killed
"ospid (28342)" => this is the OS pid of the process which opiodris aborting
"as a result of" => this precedes the error message which is thereason for opiodr to kill the process
"ORA-28" => this is the reason that opiodr killed the process. Inthis case, it is ora-28.

 

 

参考:

"opiodr abortingprocess" Messages in Alert.Log [ID 1230858.1]

Bug 6377339 - Misleading alertlog message for "opiodr aborting" [ID 6377339.8]

 

 

2.2 opiodr aborting process unknown ospid (29942) as a resultof ORA-609

 

这里表示进程ospid (29942) 因为ORA-609的错误而被kill。导致这个错误的原因有2种:

(1) Bug9856585 - "audit network by access does not audit ora-12650"

       该bug 存在Oracle 11.1 到 11.2 的版本中,官网对这个bug的说明如下:

The Bug9856585 is going to be fix bythe Oracle RDBMS Development team, it is currently in Work in Progress Status.

 

(2)在启动 EM Console后报该错误,该问题存在Oracle 10.1到11.2.可能是nscd 进程引起。解决方法是重启这个进程。

 

用超级用户(root)用户执行以下步骤进行重启:

1. Stop nscd daemon:
# service nscd stop 


2. Verify if any rogue processes is still running:

# ps -ef|grep nscd 

If any process is found, kill the roguenscd process

# kill -9 <nscd_pid> 

3. Start nscd daemon:

# service nscd start 

 

4. As the OS user who has installed theAgent, start the Agent:
cd <AGENT_HOME>/bin
emctl start agent 

 

 

参考:

Audit Network Does Not Work When notSuccessful in Oracle 11gR2 [ID 1241325.1]

Grid Control Agent 10.2 Crashes with CoreDump if 'nscd' daemon is Hung on Linux OS [ID 430200.1]

Lsnrctl Status is Failing and Alert.logShows TNS-12537 and ORA-609 [ID 950135.1]

 

 

2.3 opidcl aborting process unknown ospid (9702) asa result of ORA-604

 

根据2.1 中的说明,这里的信息时记录了ospid(9702) 进程因为ORA-604的错误而被中断了。 该消息仅用来记录进程异常退出的信息,是Oracle 11g中新增加的消息。

 

 

 

 

三.小结:

       在Oracle 11g中,新增了一个新的消息机制,会在alert log中记录异常退出的进程。

 

其消息格式示例如下:

"opiodr aborting process unknown ospid(28342) as a result of ORA-28"

解释:

"unknown" => means it is not abackground or shadow process that is killed
"ospid (28342)" => this is the OS pid of the process which opiodris aborting
"as a result of" => this precedes the error message which is thereason for opiodr to kill the process
"ORA-28" => this is the reason that opiodr killed the process. Inthis case, it is ora-28.

 

这个是Oracle 11.2 以后的格式,在11.2 之前的格式:

ORA-28 : opiodr aborting process unknownospid (21016_3086862016)

 

这种格式因为会让人迷惑,因此该格式被称为Bug 6377339,并在11.2中修改了这个格式。

 

Alert log中的"opiodr aborting processunknown ospid (28342) as a result of ORA-28"消息仅仅是一个记录信息。最后的ORA-XX的信息代表导致进程异常退出的原因。

 

 

 

 

 

 

 

 

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

版权所有,文章允许转载,但必须以链接方式注明源地址,否则追究法律责任!

QQ:492913789

Email:ahdba@qq.com

Blog:  http://www.cndba.cn/dave

Weibo: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

Linkedin: http://cn.linkedin.com/in/tianlesoftware

 

 

-------加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请----

DBA1 群:62697716(满);   DBA2 群:62697977(满)  DBA3 群:62697850(满)  

DBA 超级群:63306533(满);  DBA4 群:83829929   DBA5群: 142216823

DBA6 群:158654907    DBA7 群:172855474   DBA总群:104207940

版权声明: https://blog.csdn.net/tianlesoftware/article/details/7829166

opiodr aborting process unknown ospid (26147) as a result of ORA-28

今天在a  opiodr aborting process unknown ospid (26147) as a result of ORA-28 Errors in file /opt/app/...
  • jumewo
  • jumewo
  • 2014年09月28日 10:33
  • 1526

opiodr aborting process unknown ospid (1100) as a result of ORA-609

环境:Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 告警文件内容: Fatal NI connect error 12537,...
  • qq_20887211
  • qq_20887211
  • 2016年10月10日 09:41
  • 3159

ORA-02396错误的处理办法

2396ORA-02396: exceeded maximum idle time, please connect again0insert into agent_task(TASK_ID,TYPE,...
  • jaguarcts
  • jaguarcts
  • 2004年08月17日 18:53
  • 6806

[Oracle] opiodr aborting process unknown ospid (***) as a result of ORA-609

今天线上数据库(版本11.2.0.1)无法建立新连接,但原有的连接不受影响,alert.log报如下错误: opiodr aborting process unknown ospid (22997)...
  • u010415792
  • u010415792
  • 2014年04月03日 16:13
  • 3437

ORA-609 - opiodr aborting process unknown ospid (18874448) as a result of ORA-609

ORA-609 - opiodr aborting process unknown ospid (18874448) as a result of ORA-609 分类: ORA-xxxxx...
  • ycgjdb
  • ycgjdb
  • 2014年01月10日 09:19
  • 1488

解决ORA-03113: 通信通道的文件结尾(实质是Control filesequence number mismatch)

Windows环境下的Oracle 11g在一次关机后,无法正常启动,且无法启动到mount状态,一直提示: ORA-03113: end-of-file on communication chan...
  • haiross
  • haiross
  • 2014年11月21日 17:13
  • 40220

ORA-600错误-进程丢失

问题描述: oracle的alert日志信息如下: Thu Oct 17 10:17:54 2013 Starting ORACLE instance (normal) LICENSE_MAX...
  • linux_wang130
  • linux_wang130
  • 2013年10月17日 15:44
  • 1505

opiodr aborting process unknown ospid (24117442) as a result of ORA-609

adding some parameters into sqlnet.ora( both server and client). DIAG_ADR_ENABLED = off           ...
  • hkyw000
  • hkyw000
  • 2013年07月02日 16:59
  • 776

有关 ORA-00604 错误的总结

 ORA-00604 error occurred at recursive SQL level string Cause:An error occurred while processing a r...
  • tianlesoftware
  • tianlesoftware
  • 2009年11月08日 19:58
  • 75505

ORA-609 - opiodr aborting process unknown ospid (18874448) as a result of ORA-609

ORA-609 - opiodr aborting process unknown ospid (18874448) as a result of ORA-609 alert.log, trace,...
  • deanza
  • deanza
  • 2012年12月24日 17:41
  • 8093
收藏助手
不良信息举报
您举报文章:Oracle 11g alert log 新增消息 opiodr aborting process unknown ospid (1951) as a result of ORA-28 说明
举报原因:
原因补充:

(最多只允许输入30个字)