Hi Ramick
There is no desa_lmon trace file.
I have been checking with the RAC alert log file and I noticed that just 1 minute before the time DESA instance failed RAC was stopped. I wonder how can a RAC shutdown affect other instances in the same server?
DESA (the NON-RAC instance) failed at 2006-07-08 09:33:26.633
Here is the alert log file for the RAC: ------------------------------------------------------ Sat Jul 8 09:32:34 2006 Reconfiguration started (old inc 2, new inc 3) List of nodes: 1 Global Resource Directory frozen one node partition Communication channels reestablished Master broadcasted resource hash value bitmaps Non-local Process blocks cleaned out Resources and enqueues cleaned out Resources remastered 8760 27495 GCS shadows traversed, 0 cancelled, 9072 closed 8236 GCS resources traversed, 0 cancelled 31745 GCS resources on freelist, 39981 on array, 39981 allocated set master node info Submitted all remote-enqueue requests Update rdomain variables Dwn-cvts replayed, VALBLKs dubious All grantable enqueues granted 27495 GCS shadows traversed, 0 replayed, 9072 unopened Submitted all GCS remote-cache requests 0 write requests issued in 18423 GCS resources 2 PIs marked suspect, 0 flush PI msgs Sat Jul 8 09:32:35 2006 Reconfiguration complete Post SMON to start 1st pass IR Sat Jul 8 09:32:35 2006 Instance recovery: looking for dead threads Instance recovery: lock domain invalid but no dead threads Sat Jul 8 09:32:36 2006 Shutting down instance: further logons disabled Shutting down instance (immediate)
TIA
Is there a recent file like: /u01/app/oracle/admin/DESA/bdump/desa_lmon*
What is the full version of the database?
Are there any other traces in bdump or udump for this instance near the time of the failure?
Is there anything in other instance(s) logs - alert, bdump, udump?
BTW, an instance is the processes and memory - it would be separate from the RAC instance and should not affect it. ________________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of LS Cheng Sent: Thursday, July 27, 2006 3:00 AM To: kevinc@xxxxxxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: ORA-00481: LMON process terminated with error
Hi
Alert shows this:
Sat Jul 8 09:33:26 2006 Errors in file /u01/app/oracle/admin/DESA/bdump/desa_pmon_17392.trc: ORA-00481: LMON process terminated with error Sat Jul 8 09:33:26 2006 PMON: terminating instance due to error 481 Instance terminated by PMON, pid = 17392
desa_pmon_17392.trc shows this
*** 2006-07-08 09:33:26.634 *** SESSION ID:(1.1) 2006-07-08 09:33:26.633 error 481 detected in background process ORA-00481: LMON process terminated with error ksuitm: waiting for [5] seconds before killing DIAG
Nothing more
Tia
On 7/25/06, Kevin Closson < kevinc@xxxxxxxxxxxxx> wrote: > > error 481 detected in background process > ORA-00481: LMON process terminated with error > ksuitm: waiting for [5] seconds before killing DIAG
...and I forgot to mention that this 5 second delay is quite often not enough time to get all the DIAG output....especially in chaotic scenarios... you might consider setting the following so you at least get some info... as always, the standard "underbar" parameter setting taboos apply
_ksu_diag_kill_time = 30
> > I understand that error should apply to a RAC database. I am not able > to find out why the database failed. Any lights?
-- //www.freelists.org/webpage/oracle-l