Thank you, Tanel, for explaining the "idle blocker" ASH pattern. Your blog post
is the only place I've seen this concept explicitly mentioned.
ash_wait_chains 0.4 indeed shows the "idle blocker":
@ash_wait_chains.sql session_id||':'||event2 "session_id=2231"
"to_date('11.06.2019 07:08:00','dd.mm.yyyy hh24:mi:ss')" "to_date('11.06.2019
07:09:20','dd.mm.yyyy hh24:mi:ss')"
-- Display ASH Wait Chain Signatures script v0.4 BETA by Tanel Poder (
http://blog.tanelpoder.com ;)
%This SECONDS AAS
------ ---------- ----------
WAIT_CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FIRST_SEEN LAST_SEEN
------------------- -------------------
76% 37 .5
-> 2231:log file switch (private strand flush incomplete) -> [idle blocker
,736,37666 (oracle@svavt02a (LGWR))]
2019-06-11 07:08:30 2019-06-11 07:09:19
16% 8 .1
-> 2231:log file switch (private strand flush incomplete) -> 736:enq: CF -
contention -> 757:db file single write
2019-06-11 07:08:41 2019-06-11 07:09:03
4% 2 0
-> 2231:log file switch (private strand flush incomplete) -> 736:control file
sequential read
2019-06-11 07:08:37 2019-06-11 07:08:48
2% 1 0
-> 2231:log file switch (private strand flush incomplete) -> 736:ON CPU
2019-06-11 07:08:56 2019-06-11 07:08:56
2% 1 0
-> 2231:log file switch (private strand flush incomplete) -> 736:LGWR all
worker groups -> [idle blocker ,778,64901 (oracle@svavt02a (LG00))]
2019-06-11 07:08:34 2019-06-11 07:08:34
Similarly to the problem described in your blog post, the idle LGWR was waiting
on DBWR to complete. We can deduce this from the description of the event "log
file switch (private strand flush incomplete)", see
https://docs.oracle.com/database/121/REFRN/GUID-7F3D1BA7-2390-4911-B9E7-D2B26088F45D.htm#REFRN00583
:
"User sessions trying to generate redo, wait on this event when LGWR waits for
DBWR to complete flushing redo from IMU buffers into the log buffer; when DBWR
is complete LGWR can then finish writing the current log, and then switch log
files."
In my case, the IO write performance slumped for a moment without any obvious
reason - the load was insignificant. Next, I'm going to setup OS diagnostic (
https://github.com/brendangregg/dtrace-cloud-tools/blob/master/zfs/zfsslower.d ;
) to verify the write outliers from the OS perspective and start the analysis
from there.
Best regards,
Nenad
https://nenadnoveljic.com/blog
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">p { font-family: Arial;font-size:9pt }</style>
</head>
<body>
<p>
<br>Important Notice</br>
<br />
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee you
should in particular not disseminate, distribute, modify or copy this e-mail.
Please notify the sender immediately by e-mail, if you have received this
message by mistake and delete it from your system.<br />
Without prejudice to any contractual agreements between you and us which shall
prevail in any case, we take it as your authorization to correspond with you by
e-mail if you send us messages by e-mail. However, we reserve the right not to
execute orders and instructions transmitted by e-mail at any time and without
further explanation.<br />
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of Vontobel
Holding Ltd. and any of its affiliates (hereinafter collectively referred to as
"Vontobel Group") for any damages resulting from e-mail use is excluded. You
are advised that urgent and time sensitive messages should not be sent by
e-mail and if verification is required please request a printed version.</br>
Please note that all e-mail communications to and from the Vontobel Group are
subject to electronic storage and review by Vontobel Group. Unless stated to
the contrary and without prejudice to any contractual agreements between you
and Vontobel Group which shall prevail in any case, e-mail-communication is for
informational purposes only and is not intended as an offer or solicitation for
the purchase or sale of any financial instrument or as an official confirmation
of any transaction.<br />
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your consent
to forward you commercial communications. You can exercise, at any time and
under the terms established under current regulation, your rights. If you
prefer not to receive any further communications, please contact your client
relationship manager if you are a client of Vontobel Group or notify the sender.
Please note for an exact reference to the affected group entity the corporate
e-mail signature.
For further information about data privacy at Vontobel Group please consult <a
href="https://www.vontobel.com";>www.vontobel.com</a>.<br />
</p>
</body>
</html>
