Re: Cursor cache hit ratio over 100%

From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 5 Jun 2023 13:49:27 -0400
Message-ID: <CALcG2D+eJ3dSD23jV7kbdA84fWhtFTgxyYZGg4a9kWucvpvY_A_at_mail.gmail.com>



Yeah, Connor has destroyed the venerable Method-C.

On Mon, Jun 5, 2023, 12:44 Paul Drake <bdbafh_at_gmail.com> wrote:

> Did Connor write a routine to pick your cursor cache hit ratio?
>
>
> https://connor-mcdonald.com/2017/11/07/buffer-cache-hit-ratio-blast-from-the-past/
>
> On Mon, Jun 5, 2023, 09:51 Ghassan Salem <salem.ghassan_at_gmail.com> wrote:
>
>> There are some very old bugs about this thing. All closed as 'not a bug',
>> as it seems that some components, e.g. parts of PL/SQL, increment the
>> cursor cache hit count, while not incrementing the parse count, making the
>> CC hot ratio become >100.
>>
>> regards
>>
>>
>> On Mon, Jun 5, 2023 at 1:38 PM Mladen Gogala <gogala.mladen_at_gmail.com>
>> wrote:
>>
>>> On 6/5/23 03:45, Nenad Noveljic wrote:
>>>
>>> Is there some explanation for Cursor Cache Hit Ratio over 100% or is it
>>> a bug?
>>>
>>>
>>> select metric_name, value, metric_unit from v$sysmetric where
>>> metric_name = 'Cursor Cache Hit Ratio';
>>>
>>>
>>> METRIC_NAME VALUE METRIC_UNIT
>>>
>>> ----------------------------------------------------------------
>>> ---------- ----------------------------------------------------------------
>>>
>>> Cursor Cache Hit Ratio 110 % CursorCacheHit/SoftParse
>>>
>>>
>>> Best regards,
>>>
>>> Nenad
>>>
>>> Looks like a bug to me. What would 110% cursor hit ratio even mean? 100%
>>> means that all cursors the instance opens are in the shared pool. I can't
>>> think of any explanation for the 110%, except maybe for the North Korean
>>> voting system.
>>>
>>> Regards
>>>
>>> --
>>> Mladen Gogala
>>> Database Consultant
>>> Tel: (347) 321-1217https://dbwhisperer.wordpress.com
>>>
>>>

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jun 05 2023 - 19:49:27 CEST

Original text of this message