Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Event 'db file seq. read' stuck for hours on the same file#/block# ?
Hi,
We have a procedure that makes the sessions that call it hang for
hours, and I see in V$SESSION_WAIT the event 'db file sequential
read' showing the same file number and block number ALL THE TIME
it keeps hanging (in fact I never waited until it ended but always
killed the sessions).
Is it a normal behaviour ? It's all the more peculiar as the file and block id's point to an index block, created on a empty table ! Nothing moves, everything seems to be stalled to death. The fields p1/p2/p3text and p1/p2/p3 keep showing me the same file#, block# and blocks values: 12, 37173, 1...
Any idea about what's going on please ?
(Oracle 8.1.7.4 64-bit on Solaris 8)
Thanks. Received on Mon Feb 28 2005 - 09:53:46 CST
![]() |
![]() |