Content-Type: multipart/alternative;
 boundary="------------RoW6oeDOBHS7fNQnwRLwEaIR"
Message-ID: <c5bdc42c-e260-d8bc-7c7e-50167fa040bb@gmail.com>
Date: Thu, 2 Feb 2023 12:45:45 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.0
Subject: Re: strange wait events
To: oracle-l@freelists.org
References: <CA+riqSUY_2w4wCgV8fHm5Y+B5a8qEEgbPsMC=JVA-i+8rD_qFg@mail.gmail.com>
 <CAOVevU7x9RfXCu=9+CsETYRWiHWJTH0xrDZ3uC2PHttkHbnL=Q@mail.gmail.com>
Content-Language: en-US
From: Mladen Gogala <gogala.mladen@gmail.com>
In-Reply-To: <CAOVevU7x9RfXCu=9+CsETYRWiHWJTH0xrDZ3uC2PHttkHbnL=Q@mail.gmail.com>
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: gogala.mladen@gmail.com
--------------RoW6oeDOBHS7fNQnwRLwEaIR
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2/2/23 11:13, Sayan Malakshinov wrote:
> Hi Laurentiu,
>
> JS - Job Scheduler
> KGL - kernel generic library
> So you need to check blocking sessions and what objects the job 
> scheduler is trying to get/pin.

There are few bugs described in MOS. 65% of time spent waiting on that 
event smells like a bug. I would advise opening a SR. Of course, if 
Oracle published the event description, you know, P1,P2 and P3 in 
V$SESSION_WAIT as well as the semantics of the event, things would be 
easier. However, Oracle doesn't seem interested in helping the customers 
debug things themselves. I guess that all those support analysts who 
demand TFA files before they even understand the problem need something 
to work on.

BTW, have you noticed that the new redo log algorithm, with the private 
strands, is completely undescribed? Nothing about redo copy latch and 
redo allocation latch any more? This is certainly not the Oracle of the 
beginning of the 21st century, when Anjo Kolk and Cary Millsap were 
doing their utmost best to document all the wait events.

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com

--------------RoW6oeDOBHS7fNQnwRLwEaIR
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 2/2/23 11:13, Sayan Malakshinov
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAOVevU7x9RfXCu=9+CsETYRWiHWJTH0xrDZ3uC2PHttkHbnL=Q@mail.gmail.com">Hi
      Laurentiu,
      <div><br>
      </div>
      <div>JS - Job Scheduler</div>
      <div>KGL - kernel generic library</div>
      <div>So you need to check blocking sessions and what objects the
        job scheduler is trying to get/pin.</div>
    </blockquote>
    <p>There are few bugs described in MOS. 65% of time spent waiting on
      that event smells like a bug. I would advise opening a SR. Of
      course, if Oracle published the event description, you know, P1,P2
      and P3 in V$SESSION_WAIT as well as the semantics of the event,
      things would be easier. However, Oracle doesn't seem interested in
      helping the customers debug things themselves. I guess that all
      those support analysts who demand TFA files before they even
      understand the problem need something to work on.</p>
    <p>BTW, have you noticed that the new redo log algorithm, with the
      private strands, is completely undescribed? Nothing about redo
      copy latch and redo allocation latch any more? This is certainly
      not the Oracle of the beginning of the 21st century, when Anjo
      Kolk and Cary Millsap were doing their utmost best to document all
      the wait events.<br>
    </p>
    <pre class="moz-signature" cols="72">-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
<a class="moz-txt-link-freetext" href="https://dbwhisperer.wordpress.com">https://dbwhisperer.wordpress.com</a>
</pre>
  </body>
</html>

--------------RoW6oeDOBHS7fNQnwRLwEaIR--
--
http://www.freelists.org/webpage/oracle-l