Lines 11-18 were not executed at all. This would have been due to the
filter operation on line 4. If you check the execution plan with
dbms_xplan.display_cursor then you will get the predicates section
(something that SQL Live Monitor reports are lacking), you should see what
it says about line 4 for clues.
Hope that helps,
Andrew
On Wed, 15 Jan 2020 at 20:01, kunwar singh <krishsingh.111@xxxxxxxxx> wrote:
Hi Listers,
I have one quick question. Does the blank column values mean those
operations are not called and do they mean 0 records returned.
SQL Text
------------------------------
select /*+ monitor */ count(9) from dba_objects
Global Information
------------------------------
Status : DONE (ALL ROWS)
Instance ID : 1
Session : KUNWAR (102:53661)
SQL ID : 74f93u44y6nmg
SQL Execution ID : 16777217
Execution Started : 01/15/2020 07:13:50
First Refresh Time : 01/15/2020 07:13:50
Last Refresh Time : 01/15/2020 07:13:50
Duration : .042713s
Module/Action : SQL*Plus/-
Service : SYS$USERS
Program : sqlplus@***
Fetch Calls : 1
Global Stats
=================================================
| Elapsed | Cpu | Other | Fetch | Buffer |
| Time(s) | Time(s) | Waits(s) | Calls | Gets |
=================================================
| 0.04 | 0.04 | 0.00 | 1 | 4085 |
=================================================
SQL Plan Monitoring Details (Plan Hash Value=1203538133)
====================================================================================================================================================
| Id | Operation | Name | Rows | Cost |
Time | Start | Execs | Rows | Mem | Activity | Activity Detail |
| | | | (Estim) | |
Active(s) | Active | | (Actual) | (Max) | (%) | (# samples) |
====================================================================================================================================================
| 0 | SELECT STATEMENT | | | |
1 | +0 | 1 | 1 | | | |
| 1 | SORT AGGREGATE | | 1 | |
1 | +0 | 1 | 1 | | | |
| 2 | VIEW | DBA_OBJECTS | 89023 | 3031 |
1 | +0 | 1 | 91210 | | | |
| 3 | UNION-ALL | | | |
1 | +0 | 1 | 91210 | | | |
| 4 | FILTER | | | |
1 | +0 | 1 | 91210 | | | |
| 5 | HASH JOIN | | 89326 | 392 |
1 | +0 | 1 | 91210 | 2M | | |
| 6 | INDEX FULL SCAN | I_USER2 | 125 | 1 |
1 | +0 | 1 | 125 | | | |
| 7 | HASH JOIN | | 89326 | 391 |
1 | +0 | 1 | 91210 | 2M | | |
| 8 | INDEX FULL SCAN | I_USER2 | 125 | 1 |
1 | +0 | 1 | 125 | | | |
| 9 | TABLE ACCESS FULL | OBJ$ | 89326 | 389 |
1 | +0 | 1 | 91210 | | | |
| 10 | TABLE ACCESS FULL | USER_EDITIONING$ | 1 | 2 |
1 | +0 | 885 | 1 | | | |
| 11 | NESTED LOOPS SEMI | | 1 | 2 |
| | | | | | |
<<<<<<< See no entries for Rows(Actual) and other columns
for id 11-18
| 12 | INDEX SKIP SCAN | I_USER2 | 1 | 1 |
| | | | | | |
| 13 | INDEX RANGE SCAN | I_OBJ4 | 1 | 1 |
| | | | | | |
| 14 | TABLE ACCESS FULL | USER_EDITIONING$ | 1 | 2 |
| | | | | | |
| 15 | NESTED LOOPS | | 1 | |
| | 1 | | | | |
| 16 | INDEX FULL SCAN | I_LINK1 | 1 | |
| | 1 | | | | |
| 17 | TABLE ACCESS CLUSTER | USER$ | 1 | |
| | | | | | |
| 18 | INDEX UNIQUE SCAN | I_USER# | 1 | |
| | | | | | |
====================================================================================================================================================
--
Cheers,
Kunwar
