Re: Reporting an optimizer bug

From: Jonathan Lewis <jlewisoracle_at_gmail.com>
Date: Mon, 24 Jan 2022 09:17:09 +0000
Message-ID: <CAGtsp8=W=-uRSRKsWP1+2CtSijZimkn2eD6b0_xHpcRrVOPJQg_at_mail.gmail.com>



Your description sounds like a known bug - but that may be a coincidence. I used the following set of words for a google search: EM13 tablesace management slow query
The first hit was a reference to MOS Doc id: Enterprise Manager 10g to 12c - Tablespace Data Query shows as Top SQL and Runs Slow (Doc ID 1327378.1
The fact that the title limits itself to 12c doesn't necessarily mean that you won't see the same in EM13.

On Mon, 24 Jan 2022 at 07:23, Nilo Segura <nilosegura_at_gmail.com> wrote:

> 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 - 10:17:09 CET

Original text of this message