Re: Question on 19C Optimizer

From: Lok P <loknath.73_at_gmail.com>
Date: Sun, 25 Jul 2021 00:00:52 +0530
Message-ID: <CAKna9VaxeN4H3nX9xmqVajej8P0rMAkq4xXymAn0mxTf68odAw_at_mail.gmail.com>



Actually we have infra team who tests/evaluates which version is fine wrt stability and security and then agreed up on by the management to move all the databases to that version. But not sure if this is a miss with respect to that evaluation or its because of some dependency with the third party application is moved to this specific version. Yet to find that out.

On Sat, 24 Jul 2021, 10:45 pm Mladen Gogala, <gogala.mladen_at_gmail.com> wrote:

> When migrating, why not migrate to the latest release? And that is 19.12.
> Yes, object-relational mappers can produce ghastly queries. And if you need
> to add hints, you can always create a baseline or use
> DBMS_SQLDIAG.CREATE_SQLPATCH.
> On 7/24/21 7:28 AM, Lok P wrote:
>
>
> This bug looks too generic and so we are a bit worried as we just can't go
> adding leading hints for all queries. But then considering so many
> application runs on the below 19.9 versions, wanted to know from experts
> here if this occurs only on certain situation? Or we really have to have
> patch for this before migrating to 19C?
>
> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217https://dbwhisperer.wordpress.com
>
> -- http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l
Received on Sat Jul 24 2021 - 20:30:52 CEST

Original text of this message