Re: Convert PLSQL update with forall

From: Jacek Gębal <jgebal_at_gmail.com>
Date: Sun, 20 May 2018 23:38:54 +0100
Message-ID: <CACQ9E3tvFDzBvUdn9sxAB20=Eq=RjTnBpK7FNM-ByBdorEBb5g_at_mail.gmail.com>



If Query takes 1 hour I would look at it first. Housing with bulk update should give you a nice boost thought.

On Sun, 20 May 2018, 22:30 amonte, <ax.mount_at_gmail.com> wrote:

> Hello Andy
>
> The SQL takes around 1 hour, the updates takes around another 2000 seconds
> or so. I will check the recommendations from Jacek, Pawel and Vikas. Look
> promising.
>
> Thank you
>
> 2018-05-20 23:14 GMT+02:00 Andy Sayer <andysayer_at_gmail.com>:
>
>> What sort of timings are you actually getting here and what do you need
>> to be getting?
>>
>> Have you looked into where the time is really going? The performance
>> impact of 2 million (*2) context switches isn’t negligable but it’s not
>> going to turn something from way too slow to okay.
>>
>> How long does the SQL in your for cursor take to execute and fetch 2
>> million results?
>> How long does one individual update take? Have you looked at the
>> execution plan of that?
>>
>> Are you updating a table that you are querying inside that loop? (Causing
>> you to read undo you’ve just generated)
>>
>> Hopefully that gets us looking in the right direction,
>> Andrew
>>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Mon May 21 2018 - 00:38:54 CEST

Original text of this message