The V$ views increment EXECUTIONS when the statement completes. AWR
employs information snapshot from the V$ views. So this means that the
SQL statement has not yet completed execution by the time the AWR
snapshot was taken.
On 9/21/15 6:53, Michael Calisi wrote:
What's it mean when executions = 0
LSQL ordered by Elapsed Time DB/Inst: CG/cg Snaps: 27920-27921
-> Resources reported for PL/SQL code includes the resources used by all SQL
statements called by the code.
-> % Total DB Time is the Elapsed Time of the SQL statement divided
into the Total Database Time multiplied by 100
-> %Total - Elapsed Time as a percentage of Total DB time
-> %CPU - CPU Time as a percentage of Elapsed Time
-> %IO - User I/O Time as a percentage of Elapsed Time
-> Captured SQL account for 43.1% of Total DB Time (s): 3,709
-> Captured PL/SQL account for 115.5% of Total DB Time (s): 3,709
Elapsed Elapsed Time
Time (s) Executions per Exec (s) %Total %CPU %IO SQL Id
---------------- -------------- ------------- ------ ------ ------ -------------
1,812.7 0 N/A 48.9 1.9 98.4 9cj72br7s0wgq
BEGIN SYS.KUPW$WORKER.MAIN('SYS_EXPORT_TABLE_01', 'SYSTEM', 0); END;
1,810.5 0 N/A 48.8 8.7 92.5 6mcpb06rctk0x
Module: DBMS_SCHEDULER
call dbms_space.auto_space_advisor_job_proc ( )
