Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: ORA-00481: LMON process terminated with error
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:
TIA
On 7/27/06, ramick <ramick_at_dotster.com> wrote:
>
> 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_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of LS Cheng
> Sent: Thursday, July 27, 2006 3:00 AM
> To: kevinc_at_polyserve.com
> Cc: oracle-l_at_freelists.org
> 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_at_polyserve.com> 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?
>
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Jul 28 2006 - 01:16:58 CDT
![]() |
![]() |