Re: DBWR timed-out, what causes this?

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Wed, 27 Jan 1999 20:34:35 -0000
Message-ID: <917469260.2590.0.nnrp-02.9e984b29@news.demon.co.uk>

It would be worth checking the hardware in case one disc is throwing large numbers of write errors, causing writers to keep re-trying.

Also, are there any trace files dumped for the slaves that might give a clue.

The other thing worth doing is finding our the session ids for the slave writers when the database starts, and monitor v$session_event for those SIDs, taking change values every 10 minutes and looking for extreme values.

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

skubiszewski_at_Eisner.DECUS.Org wrote in message ...
>We are running Oracle v7.2.3 on HP-UX v10.01 in a production
>environment with ~1200 users. It's been running fairly
>well since 1997... until this past Monday.
>
>The database died Monday night and the only clue I have
>is a trace file from the DBWR with ORA-7404: sfareq:
>Time-out occurred waiting for request to complete.
>Cause: The master database writer timed out waiting
>for a write or close to complete. One of the database
>writers may have stopped running.
>
Received on Wed Jan 27 1999 - 14:34:35 CST