This content has been marked as final. Show 4 replies
All 3 are related to monitoring the sql executions and get detailed information about sql, how many current reads,consistent reads etc were needed during the execution of sql.
10053 is more advanced version of 10046 and shows more details like what all execution plans were looked on by optimizer and which plan was finally choosen. The information provided is not plain simple English and hence is mainly used by people doing advanced tuning or by oracle support.
ok, but at what circumstance they are useful?
still it is using along with alter session ??
is there is any equivalent option in dbms_monitor or any other packages ??
Check the below document
10046 is the trace event to find out the wait happening at different steps of the execution whereas 10053 is going to bring out the details of the optimizer's working. So two different trace events for two different purposes.