Re: Working out which part of an explain plan is being currently executed

From: John Hurley <johnthehurley_at_gmail.com>
Date: Wed, 23 Jan 2013 07:45:05 -0800 (PST)
Message-ID: <2a188dd6-6ab0-45e8-b888-1d93c15146ec_at_n8g2000yqd.googlegroups.com>

On Jan 23, 10:03 am, dba cjb <chris.br..._at_providentinsurance.co.uk> wrote:
> I have a big query running / as a starting point i would like to drill
> down and work out which execution steps are currently being
> executed...
> ...or which objects are being accessed
> this may give me a starting point to analyzing potential for
> performance improvement. My query has been running for a day
>
> I have tried tracing but just get a load of wait events ( see below )
> ..my only general gut feeling is that nested loops may be wronglly
> selected
>
> Any pointers or suggestions for further education gratefully received
>
> regards
> Chris B
>
> AIT #1188826856: nam='PX Deq: Execute Reply' ela= 6555 sleeptime/
> senderid=200 passes=1 p3=0 obj#=-1 tim=1729507286272
> WAIT #1188826856: nam='PX Deq: Execute Reply' ela= 13407 sleeptime/
> senderid=200 passes=1 p3=0 obj#=-1 tim=1729507299754
> WAIT #1188826856: nam='PX Deq: Execute Reply' ela= 19983 sleeptime/
> senderid=200 passes=1 p3=0 obj#=-1 tim=1729507319871
> WAIT #1188826856: nam='PX Deq: Execute Reply' ela= 6461 sleeptime/
> senderid=200 passes=1 p3=0 obj#=-1 tim=1729507326459
> WAIT #1188826856: nam='PX Deq: Execute Reply' ela= 25443 sleeptime/
> senderid=200 passes=1 p3=0 obj#=-1 tim=1729507352001
> WAIT #1188826856: nam='PX Deq: Execute Reply' ela= 12178 sleeptime/
> senderid=200 passes=1 p3=0 obj#=-1 tim=1729507364343

Do you have licenses for OEM / diagnostics pack / tuning pack?

The SQL Monitoring GUI shows where your query is executing at ... Received on Wed Jan 23 2013 - 16:45:05 CET