Re: PX Deq: Table Q qref

You could try setting event 10391,
levels 64, 512, and 2048 are likely to be the most informative for you problem.

Add the values together to run all three at once. The level is a bit flag that goes up to a total of 8191 - but when you set 8191 it looks as if a couple of the flags may disable each other.

The trace file is usually a little way behind real time - you can try:

    oradebug setospid {slave o/s pid}
    oradebug flush
to get the last bit out.

The "Execute Reply" is a slave that has
sent all it's data and is waiting for new instructions from the co-ordinator - typically a 'die' command.

You are dumping a lot of data to a spool file - you haven't exceeded the file size that
SQL*Plus can managed have you ? Perhaps something is going wrong there.

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Author of:
Practical Oracle 8i: Building Efficient Databases

Next Seminar - Australia - July/August
http://www.jlcomp.demon.co.uk/seminar.html

Host to The Co-Operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html

-----Original Message-----
To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> Date: 11 April 2002 23:25

|All
|
|I have some more information on this. I turned on event 10046 on
this. From
|this I was able to note the following...
|
|1. I start the sql script and spool the results
|
|2. It waits for less than a second on "process startup" and "PX Deq:
Join
|ACK". I think these are waits for starting up the parallel query
slaves and
|then they acknowledging the startup.
|
|3. Then it starts waiting on "PX Deq Credit: need buffer" and "PX Deq
|Credit: send blkd". I think these are when PQ actually returns data
to the
|QC
|
|4. Then it starts witing on "PX Deq: Execute Reply". I see numerous
waits on
|this. I am not sure on what this wait means.
|
|5.After two hours, it starts waiting on "PX Deq: Table Q qref" and
"SQL*Net
|message to client". By this time, it has finished writing to the
spool file.
|I verified this from the unix timestamp. The trace also shows "FETCH
|#1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=15,dep=0,og=4,tim=57419669"
|
|6. After about 3-4 hours later the SQL prompt returns to me. During
this
|time it has not written to the spool file. So I am not sure what is
being
|done in this time...
|
|What is it doing during the Step5 desciribed above? Also why does it
show
|"Fetch" when I have already gotten the data..
|
|

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jonathan Lewis
  INET: jonathan_at_jlcomp.demon.co.uk

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).