Oracle 11g alert log 新增消息 opiodr aborting process unknown ospid (1951) as a result of ORA-28 说明
一．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的信息代表导致进程异常退出的原因。
-------------------------------------------------------------------------------------------------------
版权所有，文章允许转载，但必须以链接方式注明源地址，否则追究法律责任!
Skype: tianlesoftware
Email: [email protected]
Blog: http://www.tianlesoftware.com
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