Home » RDBMS Server » Server Administration » ORA-1092 : opiodr aborting process (Oracle 11.1.0.7.0 , Linux 2.6)
ORA-1092 : opiodr aborting process [message #618423] Fri, 11 July 2014 11:25 Go to next message
Database admin
Messages: 365
Registered: September 2006
Location: india
Senior Member

Hi,

I found database down.When i checked in alert log i found some errors.
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
Error occured while spawning process m001; error = 2097
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (13452_47006397374928)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (22359_46998378852816)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (22281_47883182965200)
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (24813_47427205538256)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (1109_47358283338192)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (24715_47645794148816)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (30327_47942272070096)
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3848_46986342765008)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (32496_46941510586832)


Note : -Database was down for 3 hours and running fine now.

Also in the related trace file i found the following error.
ORA-02097: parameter cannot be modified because specified value is invalid

Could you tell me what is root cause of this error and how to avoid it in future?

Regards,
Srini

[Updated on: Fri, 11 July 2014 11:31]

Report message to a moderator

Re: ORA-1092 : opiodr aborting process [message #618425 is a reply to message #618423] Fri, 11 July 2014 11:31 Go to previous messageGo to next message
Michel Cadot
Messages: 59427
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

ORA-01092: ORACLE instance terminated. Disconnection forced
 *Cause:  The instance this process was connected to was terminated
            abnormally, probably via a shutdown abort. This process
            was forced to disconnect from the instance.
 *Action: Examine the alert log for more details. When the instance has been
          restarted, retry action.

Quote:
Also in the related trace file i found the following error.


When? 3 years before? How could we know if it is related or not if you don't post COMPLETE information.

Re: ORA-1092 : opiodr aborting process [message #618427 is a reply to message #618423] Fri, 11 July 2014 11:34 Go to previous messageGo to next message
BlackSwan
Messages: 22911
Registered: January 2009
Senior Member
>(Oracle 11.1.0.7.0 , Linux 2.6)
AFAIK, above is not a supported combination of OS version & Oracle version.

is GOOGLE broken for you?
Re: ORA-1092 : opiodr aborting process [message #618433 is a reply to message #618427] Fri, 11 July 2014 11:53 Go to previous messageGo to next message
Database admin
Messages: 365
Registered: September 2006
Location: india
Senior Member

Hi Blackswan,
Quote:
is GOOGLE broken for you?

I found the below one in google so to know root cause and action i posted my question here.
Quote:
ORA-01092: ORACLE instance terminated. Disconnection forced
*Cause: The instance this process was connected to was terminated
abnormally, probably via a shutdown abort. This process
was forced to disconnect from the instance.
*Action: Examine the alert log for more details. When the instance has been
restarted, retry action.


Hi Michel,
Quote:
How could we know if it is related or not if you don't post COMPLETE information.

Please find below the complete alert log entry.
Fri Jul 11 11:27:40 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
Error occured while spawning process m001; error = 2097
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (13452_47006397374928)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (22359_46998378852816)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (22281_47883182965200)
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (24813_47427205538256)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (1109_47358283338192)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (24715_47645794148816)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (30327_47942272070096)
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3848_46986342765008)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (32496_46941510586832)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3846_47209959240144)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3858_47010821951952)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (24762_47048898478544)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3854_47419214672336)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3809_47997534233040)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3860_47661855175120)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3904_47282087244240)
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (3821_47915375292880)
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting processFri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process

Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
[b]Errors in file /u01/app/oracle/diag/rdbms/bread/bread/trace/BREAD_q001_45871.trc:[/b]
ORA-02097: parameter cannot be modified because specified value is invalid
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (7070_47935759094224)
Fri Jul 11 11:27:41 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (30329_47191767142864)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (1410_47037378331088)
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (31904_47532238385616)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
Fri Jul 11 11:27:41 2014
ORA-1092 : opiodr aborting process unknown ospid (30329_47191767142864)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (1410_47037378331088)
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (31904_47532238385616)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (4135_47246808265168)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (30320_46976928616912)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (30350_47997104013776)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (30352_47718469779920)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (28013_47554674774480)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:43 2014
ORA-1092 : opiodr aborting process unknown ospid (28599_47545329664464)
Fri Jul 11 11:27:43 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:44 2014
ORA-1092 : opiodr aborting process unknown ospid (1611_47199704011216)
Fri Jul 11 11:27:44 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (30352_47718469779920)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:42 2014
ORA-1092 : opiodr aborting process unknown ospid (28013_47554674774480)
Fri Jul 11 11:27:42 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:43 2014
ORA-1092 : opiodr aborting process unknown ospid (28599_47545329664464)
Fri Jul 11 11:27:43 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:44 2014
ORA-1092 : opiodr aborting process unknown ospid (1611_47199704011216)
Fri Jul 11 11:27:44 2014
ORA-1092 : opitsk aborting process
Fri Jul 11 11:27:46 2014
Instance terminated by CKPT, pid = 26205
Fri Jul 11 12:18:32 2014
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
Fri Jul 11 12:18:34 2014
PMON started with pid=2, OS id=8435
Fri Jul 11 12:18:34 2014
VKTM started with pid=3, OS id=8437 at elevated priority
VKTM running at (20)ms precision
Fri Jul 11 12:18:34 2014
DIAG started with pid=4, OS id=8441
Fri Jul 11 12:18:34 2014
DBRM started with pid=5, OS id=8443
Fri Jul 11 12:18:34 2014
PSP0 started with pid=6, OS id=8445
Fri Jul 11 12:18:34 2014
DIA0 started with pid=7, OS id=8447
Fri Jul 11 12:18:35 2014
MMAN started with pid=8, OS id=8449
Fri Jul 11 12:18:35 2014
DBW0 started with pid=9, OS id=8451
Fri Jul 11 12:18:35 2014
DBW1 started with pid=10, OS id=8453
Fri Jul 11 12:18:35 2014
DBW2 started with pid=11, OS id=8455
Fri Jul 11 12:18:35 2014
LGWR started with pid=12, OS id=8457
Fri Jul 11 12:18:35 2014
CKPT started with pid=13, OS id=8459
Fri Jul 11 12:18:35 2014
SMON started with pid=14, OS id=8461
Fri Jul 11 12:18:35 2014
RECO started with pid=15, OS id=8463
Fri Jul 11 12:18:35 2014
MMON started with pid=16, OS id=8465
Fri Jul 11 12:18:35 2014
MMNL started with pid=17, OS id=8467                               
Fri Jul 11 12:27:39 2014
Starting background process SMCO
Fri Jul 11 12:27:39 2014
SMCO started with pid=73, OS id=7163
Fri Jul 11 12:28:01 2014
Thread 1 advanced to log sequence 206822 (LGWR switch)
  Current log# 2 seq# 206822 mem# 0: /u02/oradata/truth/redo2a.log
  Current log# 2 seq# 206822 mem# 1: /u03/oradata/truth/log2b.log
Fri Jul 11 13:23:54 2014
Thread 1 advanced to log sequence 206823 (LGWR switch)
  Current log# 3 seq# 206823 mem# 0: /u02/oradata/truth/redo3a.log
  Current log# 3 seq# 206823 mem# 1: /u03/oradata/truth/log3b.log
Fri Jul 11 14:00:38 2014
Thread 1 advanced to log sequence 206824 (LGWR switch)
  Current log# 1 seq# 206824 mem# 0: /u02/oradata/truth/redo1a.log
  Current log# 1 seq# 206824 mem# 1: /u03/oradata/truth/log1b.log
Fri Jul 11 14:00:49 2014
Thread 1 advanced to log sequence 206825 (LGWR switch)
  Current log# 2 seq# 206825 mem# 0: /u02/oradata/truth/redo2a.log
  Current log# 2 seq# 206825 mem# 1: /u03/oradata/truth/log2b.log
Fri Jul 11 14:01:02 2014
Thread 1 advanced to log sequence 206826 (LGWR switch)
  Current log# 3 seq# 206826 mem# 0: /u02/oradata/truth/redo3a.log
  Current log# 3 seq# 206826 mem# 1: /u03/oradata/truth/log3b.log
Fri Jul 11 14:01:13 2014
Thread 1 cannot allocate new log, sequence 206827
Checkpoint not complete
  Current log# 3 seq# 206826 mem# 0: /u02/oradata/truth/redo3a.log
  Current log# 3 seq# 206826 mem# 1: /u03/oradata/truth/log3b.log
Thread 1 advanced to log sequence 206827 (LGWR switch)
  Current log# 1 seq# 206827 mem# 0: /u02/oradata/truth/redo1a.log
  Current log# 1 seq# 206827 mem# 1: /u03/oradata/truth/log1b.log
Fri Jul 11 14:01:26 2014
Thread 1 cannot allocate new log, sequence 206828
Fri Jul 11 14:01:26 2014
Thread 1 cannot allocate new log, sequence 206828
Checkpoint not complete
  Current log# 1 seq# 206827 mem# 0: /u02/oradata/truth/redo1a.log
  Current log# 1 seq# 206827 mem# 1: /u03/oradata/truth/log1b.log
Thread 1 advanced to log sequence 206828 (LGWR switch)
  Current log# 2 seq# 206828 mem# 0: /u02/oradata/truth/redo2a.log
  Current log# 2 seq# 206828 mem# 1: /u03/oradata/truth/log2b.log
Fri Jul 11 14:01:39 2014
Thread 1 cannot allocate new log, sequence 206829
Checkpoint not complete
  Current log# 2 seq# 206828 mem# 0: /u02/oradata/truth/redo2a.log
  Current log# 2 seq# 206828 mem# 1: /u03/oradata/truth/log2b.log
Thread 1 advanced to log sequence 206829 (LGWR switch)
  Current log# 3 seq# 206829 mem# 0: /u02/oradata/truth/redo3a.log
  Current log# 3 seq# 206829 mem# 1: /u03/oradata/truth/log3b.log
Thread 1 advanced to log sequence 206830 (LGWR switch)
  Current log# 1 seq# 206830 mem# 0: /u02/oradata/truth/redo1a.log
  Current log# 1 seq# 206830 mem# 1: /u03/oradata/truth/log1b.log
Fri Jul 11 14:01:57 2014
Thread 1 advanced to log sequence 206831 (LGWR switch)
  Current log# 2 seq# 206831 mem# 0: /u02/oradata/truth/redo2a.log
  Current log# 2 seq# 206831 mem# 1: /u03/oradata/truth/log2b.log
Thread 1 cannot allocate new log, sequence 206832
Checkpoint not complete
  Current log# 2 seq# 206831 mem# 0: /u02/oradata/truth/redo2a.log
  Current log# 2 seq# 206831 mem# 1: /u03/oradata/truth/log2b.log
Thread 1 advanced to log sequence 206832 (LGWR switch)
  Current log# 3 seq# 206832 mem# 0: /u02/oradata/truth/redo3a.log
  Current log# 3 seq# 206832 mem# 1: /u03/oradata/truth/log3b.log
Fri Jul 11 14:03:49 2014
ALTER SYSTEM ARCHIVE LOG
ALTER SYSTEM ARCHIVE LOG
Fri Jul 11 14:03:49 2014
Thread 1 cannot allocate new log, sequence 206833
Private strand flush not complete
  Current log# 3 seq# 206832 mem# 0: /u02/oradata/truth/redo3a.log
  Current log# 3 seq# 206832 mem# 1: /u03/oradata/truth/log3b.log
Thread 1 advanced to log sequence 206833 (LGWR switch)
  Current log# 1 seq# 206833 mem# 0: /u02/oradata/truth/redo1a.log
  Current log# 1 seq# 206833 mem# 1: /u03/oradata/truth/log1b.log
Fri Jul 11 14:31:59 2014
ALTER SYSTEM ARCHIVE LOG
Fri Jul 11 14:31:59 2014
Thread 1 cannot allocate new log, sequence 206834
Private strand flush not complete
  Current log# 1 seq# 206833 mem# 0: /u02/oradata/truth/redo1a.log
  Current log# 1 seq# 206833 mem# 1: /u03/oradata/truth/log1b.log
Thread 1 advanced to log sequence 206834 (LGWR switch)
  Current log# 2 seq# 206834 mem# 0: /u02/oradata/truth/redo2a.log
  Current log# 2 seq# 206834 mem# 1: /u03/oradata/truth/log2b.log
Fri Jul 11 15:16:00 2014
Thread 1 advanced to log sequence 206835 (LGWR switch)
  Current log# 3 seq# 206835 mem# 0: /u02/oradata/truth/redo3a.log
  Current log# 3 seq# 206835 mem# 1: /u03/oradata/truth/log3b.log                                                  


ORA-02097: parameter cannot be modified because specified value is invalid

The above ORA error was found in the below trace file and this trace file was found in the alert log file
when database was down,

Errors in file /u01/app/oracle/diag/rdbms/bread/bread/trace/BREAD_q001_45871.trc:

Note : -- Database came online automatically.

Regards,
Srini

[Updated on: Fri, 11 July 2014 11:59]

Report message to a moderator

Re: ORA-1092 : opiodr aborting process [message #618435 is a reply to message #618433] Fri, 11 July 2014 12:03 Go to previous messageGo to next message
Michel Cadot
Messages: 59427
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

What is in the trace file?

Re: ORA-1092 : opiodr aborting process [message #618436 is a reply to message #618435] Fri, 11 July 2014 12:05 Go to previous messageGo to next message
Database admin
Messages: 365
Registered: September 2006
Location: india
Senior Member

*** 2014-07-11 11:27:41.579
*** SESSION ID:(1055.475) 2014-07-11 11:27:41.579
*** CLIENT ID:() 2014-07-11 11:27:41.579
*** SERVICE NAME:(SYS$BACKGROUND) 2014-07-11 11:27:41.579
*** MODULE NAME:(STREAMS) 2014-07-11 11:27:41.579
*** ACTION NAME:(QMON Slave) 2014-07-11 11:27:41.579

KSV 2097 error in slave process

*** 2014-07-11 11:27:41.579
ORA-02097: parameter cannot be modified because specified value is invalid
~

[Updated on: Fri, 11 July 2014 12:08]

Report message to a moderator

Re: ORA-1092 : opiodr aborting process [message #618442 is a reply to message #618436] Fri, 11 July 2014 13:32 Go to previous messageGo to next message
Michel Cadot
Messages: 59427
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Search for any logon trigger.
Find which statement was executed by the process.

Re: ORA-1092 : opiodr aborting process [message #618454 is a reply to message #618442] Sat, 12 July 2014 00:53 Go to previous messageGo to next message
Database admin
Messages: 365
Registered: September 2006
Location: india
Senior Member

Michel,
Search for any logon trigger. -- How to find logon trigger ?
Find which statement was executed by the process. -- How to find that ?

Regards,
Srini
Re: ORA-1092 : opiodr aborting process [message #618456 is a reply to message #618454] Sat, 12 July 2014 01:23 Go to previous messageGo to next message
Michel Cadot
Messages: 59427
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Quote:
Search for any logon trigger. -- How to find logon trigger ?


select owner, trigger_name from dba_triggers where triggering_event like 'LOGON%';


Quote:
Find which statement was executed by the process. -- How to find that ?


First find which user, application, session where connected at this time in the difference catalog views. Then search for trace from this sessions, the queries, ask people what there were doing, search in the code...

Re: ORA-1092 : opiodr aborting process [message #618462 is a reply to message #618456] Sat, 12 July 2014 01:43 Go to previous message
Database admin
Messages: 365
Registered: September 2006
Location: india
Senior Member

Michel,

Thanks for your inputs.Will follow it.
Previous Topic: Connection between application and database server
Next Topic: Oracle error ora 07445
Goto Forum:
  


Current Time: Sat Oct 25 11:46:16 CDT 2014

Total time taken to generate the page: 0.08150 seconds