See below for more details. Same plan hash value but vastly different elapsed
time.
SQL_TEXT
--------------------------------------------------------------------------------
SQL_PROFILE SQL_PLAN_BASELINE
CHILD_NUMBER
---------------------------- ---------------------------- ------------
PLAN_HASH_VALUE FIRST_LOAD_TIME LAST_ACTIVE_TIME EXECUTIONS end of fetch
--------------- ------------------- ------------------- ---------- ------------
DISK_READS BUFFER_GETS BUFF_PER_EXEC DISK_PER_EXEC BUFF_ROW ROWS_EXEC
------------ ------------ ------------- ------------- ------------ ----------
HIT_RATIO SORTS_EXEC CPU_SEC CPU_SEC_PER_EXEC ELAPSED_SEC
---------- ---------- ---------- ---------------- -----------
ELAPSED_SEC_PER_EXEC I I I I object id PROGRAM_LINE# FORCE_MATCHING_SIGNATURE
-------------------- - - - - ---------- ------------- ------------------------
SELECT 1 x FROM user_tables u WHERE u.table_name='FERRYLINE' UNION SELECT 1 x
FROM all_synonyms s INNER JOIN all_tables t ON s.synonym_name=t.table_name AND
s.owner='PUBLIC' AND s.synonym_name=s.table_name WHERE
s.synonym_name='FERRYLINE' UNION SELECT 1 x FROM user_views WHERE view_name =
'FERRYLINE' UNION SELECT 1 x FROM all_synonyms s INNER JOIN all_views v ON
s.synonym_name = v.view_name AND s.owner = 'PUBLIC' AND s.synonym_name =
s.table_name WHERE s.synonym_name = 'FERRYLINE'
0
144319191 2019-10-31/13:01:22 10/31/2019 14:34:32 1
1
3 2,497 2,497 3 2,497
1
99.8798558 4 2.481887 2.481887 3.47002
3.47002 N N Y Y 0 0
14299696840961403209
SELECT 1 x FROM user_tables u WHERE u.table_name='FERRYLINE' UNION SELECT 1 x
FROM all_synonyms s INNER JOIN all_tables t ON s.synonym_name=t.table_name AND
s.owner='PUBLIC' AND s.synonym_name=s.table_name WHERE
s.synonym_name='FERRYLINE' UNION SELECT 1 x FROM user_views WHERE view_name =
'FERRYLINE' UNION SELECT 1 x FROM all_synonyms s INNER JOIN all_views v ON
s.synonym_name = v.view_name AND s.owner = 'PUBLIC' AND s.synonym_name =
s.table_name WHERE s.synonym_name = 'FERRYLINE'
1
144319191 2019-10-31/13:01:22 10/31/2019 14:20:09 7
7
0 4,509 644 0
644 1
100 4 3.2556 .465085714 6.323123
.903303286 N N N 0 0
14299696840961403209
As stated, the parent and child cursor have the same plan_hash value. The SQL"Jeffrey Beckstrom" <jbeckstrom@xxxxxxxxx> 10/31/19 2:27 PM >>>
So, to be clear, the all the cursors have the same plan ? (Both good and bad) ?Chris Taylor <christopherdtaylor1994@xxxxxxxxx> 10/31/19 2:22 PM >>>