Re: Unable to detect blocking session
From: Rich J <rjoralist3_at_society.servebeer.com>
Date: Wed, 21 Feb 2018 10:09:19 -0600
Message-ID: <a908a13b23c806777de2dc66388e704f_at_society.servebeer.com>
Date: Wed, 21 Feb 2018 10:09:19 -0600
Message-ID: <a908a13b23c806777de2dc66388e704f_at_society.servebeer.com>
On 2018/02/21 09:32, Sandra Becker wrote:
EM12 has problems with blocking lock detection, as it relies on the target's buggy DBA_OUTSTANDING_ALERTS view (or something related). I've had a chain of several SRs open regarding the entries found in that view for DB 11.2.
EM13 (at least EM13R2) thankfully ignores this and goes directly against "V$LOCK" (not "GV$LOCK", at least according to https://docs.oracle.com/cd/E73210_01/EMDBM/GUID-A530335C-B818-423E-83CE-613B263C242F.htm#oracle_database_userblock ).
So, I would hope that if you're running EM13, that you should see something. Was this a TX lock? And, if so, were your thresholds and collection schedules set for "User Locks"->"Maximum Blocked DB Time (seconds)"->"TX"?
Rich
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Feb 21 2018 - 17:09:19 CET