Oracle 11g Alert Log new message opiodr aborting process unknown ospid (1951) as a result of ORA-28 description

 

1. Alert Log description

 

In the Oracle 11.2.0.2 database, a large number of alert logs are found as follows:

 

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

 

Ii. Problem Analysis:

 

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

 

In Oracle 11.1.0.6 and 11.1.0.7, there is a bug: 6377339. It will display the following information in Alert Log:

 

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

 

This prompt information may cause us to be confused. Therefore, the bug is fixed in Oracle 11.2, and the prompt information after the fix is changed:

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

 

Opiodr aborting process is only a message. It is a new message added in Oracle 11g, used to record abnormal exit of the process.

This message is generally used to record the kill session information of a user with permissions.

 

 

Example:

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

Explanation:

"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.

 

 

Refer:

"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

 

This indicates that the process ospid (29942) is killed due to a ORA-609 error. There are two reasons for this error:

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

This bug exists in versions from Oracle 11.1 to 11.2. The official website describes this bug as follows:

The bug9856585 is going to be fix bythe Oracle RDBMS Development Team, it is currently in work in progress status.

 

(2) This error is reported after the EM console is started. It may be caused by the nscd process. The solution is to restart the process.

 

Follow these steps to restart a Super User (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

 

 

Refer:

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

 

According to the instructions in 2.1, the information here records that the ospid (9702) process was interrupted due to a ORA-604 error. This message is only used to record abnormal exit information of the process. It is a newly added message in Oracle 11g.

 

 

 

 

Iii. Summary:

In Oracle 11g, a new message mechanism is added to record abnormal exited processes in Alert Log.

 

The message format is as follows:

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

Explanation:

"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.

 

This format is later than Oracle 11.2, and earlier than 11.2:

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

 

This format is confusing, so it is called bug 6377339 and modified in 11.2.

 

The "opiodr aborting processunknown ospid (28342) as a result of ORA-28" message in the Alert Log is just a record information. The final ORA-XX information represents the cause of abnormal exit of the process.

 

 

 

 

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Skype: tianlesoftware

QQ: tianlesoftware@gmail.com

Email: tianlesoftware@gmail.com

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

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

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

 

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940