Re: Event 'db file seq. read' stuck for hours on the same file#/block# ?

From: Haximus <e_at_t.me>
Date: Tue, 01 Mar 2005 08:29:03 GMT
Message-ID: <jJVUd.30737$hN1.12728@clgrps13>

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:mr88219dle3pb9ludmqt3hmla7atu99c6o_at_4ax.com...
> On Tue, 01 Mar 2005 05:54:09 GMT, "Haximus" <e_at_t.me> wrote:
>
>>Just a thought... latch contention? 'db file seq. read'
>
> Could you please look up the definition of 'db file sequential read'
> It has exactly *nothing* to do with control file reads, and
> consequently your answer is fully incorrect and misleading.

"The session waits while a sequential read from the database is performed. This event is also used for rebuilding the controlfile, dumping datafile headers, and getting the database file headers." http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76961/apa5.htm

All I was suggesting is to check if the session is hung on a latch request:

select * from v$session_wait sw, v$latchname ln where sw.p2=ln.latch# where sw.sid=###

Are all you DBA fixtures here such ogres? ;) Received on Tue Mar 01 2005 - 02:29:03 CST