Re: Reporting an optimizer bug

From: Lothar Flatz <l.flatz_at_bluewin.ch>
Date: Mon, 24 Jan 2022 10:20:22 +0100
Message-ID: <d8efbaf5-6db7-8192-988d-1fabb34fbb7c_at_bluewin.ch>


Hi Stfan,

sure, Nigel is a good idea.

Regards

Lothar
Am 24.01.2022 um 09:35 schrieb Stefan Koehler:
> Hello Nilo,
> the magic trick is to know the right Oracle PMs :-)
>
> In your case it would be Nigel Bayliss ( https://twitter.com/vldbb ).
>
> Best Regards
> Stefan Koehler
>
> Independent Oracle performance consultant and researcher
> Website: http://www.soocs.de
> Twitter: _at_OracleSK
>
>> Nilo Segura <nilosegura_at_gmail.com> hat am 24.01.2022 08:23 geschrieben:
>>
>> Hello,
>> We have found what we believe is a bug in the optimizer, and we are trying to report this problem to Oracle with no success at all. We have found two workarounds that generate a very good plan. The problem is with one query executed by the EM 13c (related to tablespace monitoring). These are SYS related objects, so it is not possible to get all the info with dbms_sqldiag (testcase), even though support told us precisely to do that :(
>>
>> So my question is, for those of you have succeeded in reporting these issues to Oracle.. What is the magic trick ? We are hitting a wall here and it is extremely frustrating, looks like they do not want at all to open a bug report. And yes, we have escalated the SR with no positive result either.
>>
>> Best regards.
>> --
>>
>> Nilo Segura
>> Oracle Support - IT/DB
>> CERN - Geneva
>> Switzerland
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jan 24 2022 - 10:20:22 CET

Original text of this message