Re: strange wait events
Date: Thu, 2 Feb 2023 12:45:45 -0500
Message-ID: <c5bdc42c-e260-d8bc-7c7e-50167fa040bb_at_gmail.com>
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 -- http://www.freelists.org/webpage/oracle-lReceived on Thu Feb 02 2023 - 18:45:45 CET