Basics of Locks and Blocking Session in Oracle 19c

[@oracledbacafe8742]

Thanks all for 1k+ views. My first video with 1k+ views.😀

[@farheenmaheen]

for theory there are many videos, but realtime issues resolving is the key, please continue like this

[@farheenmaheen]

Saw many oracle related videos, the way your videos are, excellent. keep it up the good work.

[@eswar_yadav]

well explained

[@gudipudiseema2430]

Thanks for re-uploading this sir. Please try to update with new videos on day to day activities and issues we face in real time and how to solve those issues.. mostly weekly activities, monthly activities your content is really helpful. Thanks again for all your effort and support you provide to oracle community 🎉

[@dementors_HP]

THANK YOU SO MUCH :)

[@kondapalligopi2404]

Super

[@Manickblaze]

Sometimes we get error as pbject no longer exists. How to find out the issue in such scenarios

[@GauravSingh-bp8nw]

Thank you!!

[@sweetmemoriesSR]

Hi Sir, the session 17 is belonging to screen A where first update command ran and 149 is screen B is it correct. This always confuses in many queries, please clarify.

[@oracledbacafe8742]

Correct. Session 17 is blocking session 149. (Session 149 is waiting)

[@GauravSingh-bp8nw]

Hi sir Session 17 is being blocked by session 149 or is it reverse?? Could you please clear this doubt in simple words??

[@oracledbacafe8742]

@@GauravSingh-bp8nw It is the reverse. Session 149 is being blocked by session 17. That means, Session 149 needs the row lock to proceed with the UPDATE statement, but it hangs and wait for the lock, because Session 17 is holding the lock (Session 17 performed the UPDATE on the same row but never issued a COMMIT or ROLLBACK).

[@Vijesh4ever]

Thumbs down! You could have easily derived table detail and eventually from the locked session from v$session. Wonder why KZbinrs make it complex for viewers