Re: direct path write temp

Actually - there are underscore hints that were used to change the amount of temp you could allocate to hash and sorts and setting the work area policy to manusl, but they have the very adverse effect post 10g: PGA stops being allocated at all.
https://dbakevlar.com/2011/08/a-tale-of-session-parameter-settings/ This was only at the session level, but with enhancements to PGA, don't even consider these old settings.

Kellyn

On Thu, Sep 27, 2018 at 2:50 PM Arian Stijf <arian_at_stijf.com> wrote:

> 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
>
>
> --

[image: Kellyn Pot'Vin on about.me]

*Kellyn Pot'Vin-Gorman*
DBAKevlar Blog <http://dbakevlar.com>
President Denver SQL Server User Group <http://denversql.org/> about.me/dbakevlar

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