Re: Blocker did not identified
From: Jure Bratina <jure.bratina_at_gmail.com>
Date: Sun, 31 Dec 2017 21:59:06 +0100
Message-ID: <CAC08BHJVjze+GebTukjnp91eeeUFP+OPwwi45G7UU1PCukdQDQ_at_mail.gmail.com>
Date: Sun, 31 Dec 2017 21:59:06 +0100
Message-ID: <CAC08BHJVjze+GebTukjnp91eeeUFP+OPwwi45G7UU1PCukdQDQ_at_mail.gmail.com>
Eriovaldo,
> I need to improve this query trying to get the main BLOCKER.
> But it does not help in case of similar problem, by the time configured
for dba_hist refresh.
Maybe Tanel's dash_wait_chains.sql might help (
https://blog.tanelpoder.com/2013/11/06/diagnosing-buffer-busy-waits-with-the-ash_wait_chains-sql-script-v0-2/
).
Or, alternatively, ash_wait_chains.sql if the wait is in progress and for
some strange reason the BLOCKING_* columns in v$session aren't populated
(especially FINAL_BLOCKING_SESSION in your case).
Regards,
Jure
-- http://www.freelists.org/webpage/oracle-lReceived on Sun Dec 31 2017 - 21:59:06 CET