Re: direct path write temp

Well, for one, have several temporary tablespaces for these operations use the least used one, located on the fast storage. Second, do not use nologging in production. Ever.

On 09/27/2018 05:11 PM, Hameed, Amir wrote:
> How do I optimize my writes to GTT or a table with NOLOGGING for large inserts?
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org <oracle-l-bounce@freelists.org> On Behalf Of Arian Stijf
> Sent: Thursday, September 27, 2018 4:50 PM
> To: oracle-l_at_freelists.org; gogala.mladen_at_gmail.com
> Cc: oracle-l-bounce_at_freelists.org
> Subject: Re: direct path write temp
>
> Is that a tongue in your cheek?
>
> As far as I know there's indeed no parameter to control writes to temp space. So:
> Avoiding the writes in the first place is the best option.
> Second best is making sure enough memory is available to accommodate for the operation, so no temp space is needed.
> Third and most likely option is a combination of the above.
>
> Regards,
>
> Arian
>
> Mladen Gogala schreef op 27.09.2018 22:39:
>> No parameter controls temporary direct writes. If the hash or sort
>> doesn't fit in available PGA memory, the surplus will be written to
>> the temporary tablespace. And that's about it. So, don't use sort or
>> hash joins. Another method of avoiding writing to the temp is using
>> in-memory option, but that will cost you a pretty penny.
>>
>> Regards
>>
>> On 09/27/2018 01:13 PM, Hameed, Amir wrote:
>>
>>> Hi,
>>>
>>> I am trying to find out what database parameter controls the size of
>>> DIRECT PATH WRITE TEMP and is there way to optimize it. You feedback
>>> will be appreciated.
>>>
>>> Thank you,
>>>
>>> Amir
>> --
>> Mladen Gogala
>> Database Consultant
>> Tel: (347) 321-1217
> --
> http://www.freelists.org/webpage/oracle-l
>
>

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217

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