Re: Reporting an optimizer bug

Hello,
No, not our case. But I see that support found the first DocId because they asked us to purge the recyclebin. This did not change anything. The SQL appearing in both DocIds is not the same. The re-gathering of stats for fixed and dictionary objects did not change anything either. Only setting the optimizer features back to 11.2.0.4 or 12.1.0.2 did the trick. Later we found that a "minimal" change => _push_join_union_view=false does also help the optimizer to generate the good plan.

regards.

On Mon, Jan 24, 2022 at 10:22 AM Jonathan Lewis <jlewisoracle_at_gmail.com> wrote:

>
> Managed to hit "Send" prematurely.
>
> Signing in to MOS to follow up the details I found that it didn't quite
> match my memory of a similar bug that was raised on a forum somewhere a few
> months back, but it linked on to this one: Query Against Dictionary Views
> Extracting Tablespace Information is Slow or Appears to Hang (Doc ID
> 1292253.1)
> which includes further details that looked familiar.
>
> Is this your case?
>
> If not, do you have the SQL_ID for the query causing your problem, and
> have you searched MOS (or done a google search) for the sql_id - you may
> find that someone else has already reported it and got some bug number or
> extra information about it.
>
> Regards
> Jonathan Lewis
>
>
>
> On Mon, 24 Jan 2022 at 09:17, Jonathan Lewis <jlewisoracle_at_gmail.com>
> wrote:
>
>>
>> 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
>>>
>>

-- 
Nilo Segura
Oracle Support - IT/DB
CERN - Geneva
Switzerland

--
http://www.freelists.org/webpage/oracle-l