Interpreting Oracle Explain Plan Output - John Mullins 

full table scans are not always deceptive, considering the query not being optimized properly and hitting large tables multiple times. The explain plan would go for 'direct path read' wait events, so the optimizer will not put the query in the SGA buffer cache instead forces the execution entirely pinning against PGA. This favors the quickest output fetch with a bit downside to the I/O during the query execution.

thanks a lot for a really informative video.. Can we have examples of queries which would result in different index access method and join methods ? That would really be helpful

Cross join isn't a join method. It is a join type (like inner join) and commonly uses merge join method to accomplish

This is best video i have ever seen on explain plan

Excellent information, very useful for beginners

Very informative and helpful. Great job.

awesome explanation. thanks man. you rock

very very informative! amazing

Super explanation...Very very helpful and informative. To the point, well navigated and no crap..

How to investigate this without access to production data? Is there something to 'copy statistics' from production to a test system?

Thank you so much!

Very Helpful Video. Thank you sir :)

Great stuff! 29:12 are we talking about bitmap *indexes* ?

Thanks a lot. Very useful video.

ੳਰੇਕਲ ਜਿਂਦਾਬਾਦ

To the point explanation.

very well explained

Thanks!!!!!!! Great video.

Good explanation !! Thanks !!!

a valuable follow up video would be to see these considerations being implemented

sir how did you decide order of operations

Awesome Video. Lots of topics cleared.

Became ur fan

great video.