Re: Not able to fetch execution plan from cursor

Hello Rakesh,
no overhead - except the first run when statement is parsed (or subsequent reparses) and CBO trace is written / generated.

By the way please don't be confused about the different numbers in "Plan Table" section compared to DBMS_XPLAN. 100053 is run by C code and DBMS_XPLAN is using SQL ... so you gonna see a mix-up of 1000 and 1024 division ( https://community.oracle.com/message/14092523#14092523 ).

Best Regards
Stefan Koehler

Independent Oracle performance consultant and researcher Website: http://www.soocs.de
Twitter: _at_OracleSK

> Rakesh Ra <rakeshra.tr_at_gmail.com> hat am 29. Mai 2019 um 08:47 geschrieben:
>
> Hi Nenad,
>  
> Thanks for the quick response.
>  
> I will check with the below settings. Does this setting have any overhead to the DB? I guess the trace will be generated only when hard parse happens. 
>  
> alter system set events 'trace [SQL_Optimizer.*][sql:  fjj079nrphmwu ]'  ;
>  
> One another interesting part is that when the SQL was executing and fetching the records (as per SQL monitor) I tried to fetch the plan from cursor, even that time i failed to get the details. This same SQL execution plan hash value is shared by 24 other SQL statements and for all I am not able to fetch from cursor.
>
> Regards,
> Rakesh RA

--
http://www.freelists.org/webpage/oracle-l