This event appears when a PQ slave has nothing to
do, but is not allowed to go idle.
One scenario where you can see large values for
the event is when (for example) you have a large
data set coming out of a parallel ORDER BY.
The last layer of PX slaves in the query will receive
a ranged set
I failed to mention this is an 8.1.7.3 database. Sorry about that.
Nancy
-Original Message-
McCormick
Sent: Thursday, May 16, 2002 7:53 PM
To: Multiple recipients of list ORACLE-L
Hello,
I am hoping someone can help me with an elusive wait event called 'PX Deq:
Execution Msg'. As
Nancy:
From your message the average wait time is less than 1 micro second (if I my
undertstanding is correct) and I would not worry much about that if that is
the case.
Best Regards,
K Gopalakrishnan
Bangalore, INDIA
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL
Nancy,
Hope this helps - it is some information I have saved over time.
If someone else can help clarify this I would find it helpful too.
From Jonathan Lewis in a Metalink discussion.
The most useful giveaway is often the 'send blocked' wait -
this indicates a degree of contention as
send blocked is listed in the 9i documentation as an idle wait event. I understand
from the post that the producers are too quick for the consumer. What exactly are
these producers and what exactly is the consumer.
Ian MacGregor
Stanford Linear Acclerator Center
[EMAIL PROTECTED]
