Hi Erik,

MTS uses a common queue for incoming requests (calls) to shared servers, and
other queues for responses going back via a dispatcher. These queues and
their clients constitute the virtual circuit. When a process is ready to
take a request or response from its queue, but finds that there is nothing
there, then it waits for 'virtual circuit status' to change.

So, if you're using MTS and you're not spending a lot of time in this wait
event, then that indicates that your requests and responses are being
delayed by queue time (which incidentally is not yet picked up by StatsPack,
although it is in the V$ views, nor is it visible in the trace files because
the waiting session does not have a corresponding process that is waiting).

@   Regards,
@   Steve Adams
@   http://www.ixora.com.au/         - For DBAs
@   http://www.christianity.net.au/  - For all 

-----Original Message-----
Williams
Sent: Thursday, 28 August 2003 4:49 AM
To: Multiple recipients of list ORACLE-L


Has anyone run into excessive waits on this event? After running my
statspack through oraperf.com, I see that I am waiting ~80% of response time
on this event. I have read on metalink that this is NOT an idle event, and
on asktom.oracle.com that it IS an idle event. We have MTS configured, but
all the clients are set to use dedicated server. Should I try reduce this
event by tuning MTS or is it truely an idle event?

Thanks
Erik
 




-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Steve Adams
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to