... actually v$session_wait....!
"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<cb234n$cub$1_at_titan.btinternet.com>...
> v$event_name says that parameter 1 (p1, or p1raw)
> of v$session_wait will be the 'from process' and
> parameter 2 the timeout.
>
> I don't know if the 'from process' will be identified
> by id, or address but it should match something in
> v$process (or v$bgprocess).
>
>
> --
> Regards
>
> Jonathan Lewis
>
> http://www.jlcomp.demon.co.uk
>
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
> The Co-operative Oracle Users' FAQ
>
> http://www.jlcomp.demon.co.uk/seminar.html
> Optimising Oracle Seminar - schedule updated May 1st
>
>
> "Matt" <mccmx_at_hotmail.com> wrote in message
> news:cfee5bcf.0406180648.298bc840_at_posting.google.com...
> > Anyone have any idea how to diagnose the cause of the 'rdbms ipc
> > reply' wait event....
> >
> > A session will wait on this event when it waits for a background
> > process to respond to a request. However is there any way to
> > determine what background process..?
> >
> > This event accounts for a significant amount of the total response
> > wait during the batch run (> 40%).
> >
> > AFAIK 'rdbms ipc message' is an idle event but 'rdbms ipc reply' is
> > not.
> >
> > I've seen a note on Metalink which says that Truncating tables causes
> > DBWR to flush blocks from the cache, and while this is happening the
> > server process will wait on 'rdbms ipc reply'. We have a large buffer
> > cache which could be a cause of a high wait time on this event.
> >
> > Are there any other causes of this event...
> >
> > Matt
Received on Mon Jun 21 2004 - 02:24:55 CDT
