Re: How to avoid using the execution plan with parallel on oracle rac 19.13?
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Fri, 26 May 2023 17:09:43 -0400
Message-ID: <4c88f42a-8e3f-d2ec-683a-1f3828e36ac7_at_gmail.com>
Date: Fri, 26 May 2023 17:09:43 -0400
Message-ID: <4c88f42a-8e3f-d2ec-683a-1f3828e36ac7_at_gmail.com>
On 5/26/23 09:53, Andy Sayer wrote:
> There looks to be opportunity to tune that SQL, you’re going to the
> same gv$ view in your with clause (with a distinct and analytics) as
> you’re joining to later, presumably you should be able to just do the
> analytics in one go.
>
> Either way, this is a gv$ so needs to check each instance, so you get
> a parallel thread per instance.
>
> Why is a query against a gv$ view (which should be in memory on each
> instance) consuming IO?
>
> Thanks,
> Andy
Andy is right. Using GV$ tables always implies using parallel query because Oracle has to check every instance in the cluster. If you set "parallel_max_servers" to 0 on any cluster instance, you will disable access to GV$ tables.
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com -- http://www.freelists.org/webpage/oracle-lReceived on Fri May 26 2023 - 23:09:43 CEST