Reporting an optimizer bug
From: Nilo Segura <nilosegura_at_gmail.com>
Date: Mon, 24 Jan 2022 08:23:01 +0100
Message-ID: <CAO8HWHZf+f5eE+FCWFe38w0EihV70_no4XKGUWp2U_YTM+uKcQ_at_mail.gmail.com>
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 :(
Date: Mon, 24 Jan 2022 08:23:01 +0100
Message-ID: <CAO8HWHZf+f5eE+FCWFe38w0EihV70_no4XKGUWp2U_YTM+uKcQ_at_mail.gmail.com>
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
Received on Mon Jan 24 2022 - 08:23:01 CET