![]() NAME PARAMETER1 PARAMETER2 PARAMETER3 WAIT_CLASSĮnq: TX - row lock contention name|mode usn select p1,p2,p3,count(*) from dba_hist_active_sess_history where event = 'enq: TX - row lock contention'Ģ and sample_time between to_date(' 14:25:00','yyyy-mm-dd hh24:mi:ss') and to_date(' 15:00:00','yyyy-mm-dd hh24:mi:ss') SQL> select name,parameter1,parameter2,parameter3,wait_class from v$event_nameĢ where name = 'enq: TX - row lock contention' Therefore I've done some operation steps below, Now I wanna detailedly and seriously analyze (or try to trouble-shooting) this wait event "enq: TX - row lock contention". Select 'kill -9 '||pro.spid from v$session ses,v$process pro where ses.paddr=pro.addr and ses.event='enq: TX - row lock contention' The following is that command I executed on Linux, To restore business as soon as possible, afterwards I manually killed all of the OS processes that produced row lock contention immediately. ![]() Please take a look at my several screenshots as follows, Yesterday afternoon our production system (oracle db server 11.2.0.4.0 for Linux x86_64) has produced a large amount of wait event 'enq: TX - row lock contention'.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |