Re: LOG WRITER PROCESS

Unless I am way off base, this trace is reporting that the LGWR died *because* the DBWR, the database writer, died. To find out why, you would need to look at the DBWR trace that was hopefully generated at the same time.

No useful information about the DBWR crash will be gleaned from the LGWR trace. If no trace was generated, there are some events that can be set to determine the reason the DBWR crashed.

Good luck,

--
Jeremiah Wilton http://www.wolfenet.com/~jeremiah

On Wed, 14 Oct 1998 satar_at_my-dejanews.com wrote:
>
> So many reasons cause the log writer to crash. Did you add/change anything
> about the database (like add new software?). Main causes of crashes: Bad
> controller (either on hardware RAID,, or on internal system) Software that
> backs up an online database while the database is not in ARCHIVELOG mode.
> There are just so many reasons, your best bet is to gather all the info you
> have and have Oracle support help you out. Also, in the future, when you
> post, you should give specifics of your setup and database.

> In article <36249F57.167EB0E7_at_ornl.gov>,
> D S Tharpe <i5t_at_ornl.gov> wrote:
> > Anyone know what causes the log writer process to die? This is all that
> > is in the trace file. It happened 2 times yesterday and once already
> > this morning. Where else can I look for clues to this ?
> >
> > Tue Oct 13 17:16:56 1998
> > *** SESSION ID:(3.1) 1998.10.13.17.16.56.000
> > error 471 detected in background process
> > OPIRIP: Uncaught error 447. Error stack:
> > ORA-00447: fatal error in background process
> > ORA-00471: DBWR process terminated with error
Received on Wed Oct 14 1998 - 15:00:36 CDT