Maximum size for PGA_AGGREGATE_TARGET

From: Martin Bach <development_at_the-playground.de>
Date: Tue, 19 Jan 2010 11:57:22 +0000
Message-ID: <4B559E22.1080400_at_the-playground.de>



Dear list,

I know this may sound silly but what's the maximum size for pga_aggregate_target on a PAE kernel? Could this be defined > 2G and actually use all of that if needed?

I'd normally say that it's limited by the maximum address space for processes on 32bit systems which, depending on kernel is around 1.7-2G of memory. That's also undermined by v$pgastat statistic "maximum pga allocated".

I did some background reading and research and it appears that there is a 1-many relationship between process and workarea(s). Could a process use multiple workareas for really large sorts?

Anyway, no one should be on 32bit systems nowadays anyway if you need large amounts of memory :) I'm really more used to 64bit boxes...

I used http://www.pythian.com/documents/Working_with_Automatic_PGA.ppt as reference, but might be completely off the mark.

Regards,

Martin
--

Martin Bach
OCM 10g
http://martincarstenbach.wordpress.com
--

http://www.freelists.org/webpage/oracle-l Received on Tue Jan 19 2010 - 05:57:22 CST

Original text of this message