Re: bloom filter not used after 19C upgrade

Which version of Oracle was it working in before the upgrade. Which specific RU of 19c is it no longer appearing in, and can you compare the cardinality estimate at the point where the Bloom filter is created in the working version with the cardinality estimates in 19c. (In a simple hash join it would be the cardinality estimate of the build table - though technically it's the estimated number of distinct values rather than the estimated cardinality that matters).

Regards
Jonathan Lewis

On Wed, 8 May 2024 at 20:43, Laurentiu Oprea <laurentiu.oprea06_at_gmail.com> wrote:

> Dear all,
>
> I`m trying to figure out why a query is not using part join bloom filter
> after the 19C upgrade.
>
> In 10053 KkoBloomFIlter messages are: accepted, but final decision will be
> made in code generation. But in the final execution plan it is using
> partition range all..
>
> WHere should I look for hints to understand what exactly went wrong?
>
> Appreciate your help.
>

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