Re: PGA usage
- From: "Frits Hoogland" <frits.hoogland@xxxxxxxxx>
- To: Yavor_Ivanov@xxxxxxxx
- Date: Tue, 10 Jul 2007 16:14:57 +0200
Yavor,
I assume the /3GB switch is set (otherwise the memory available in userspace
is limited to 2GB)
The PGA memory can be monitored per session using v$sesstat. Can you
elaborate on what the report is actually doing? (I suspect a pl/sql table is
populated, which is kept in the PGA and doesn't get to the assigned
temporary tablespace like sort data or hash data.)
AFAIK, the amount of PGA memory which can be allocated by a session is only
limited to operating system imposed limits.
frits
On 7/10/07, Yavor Ivanov <Yavor_Ivanov@xxxxxxxx> wrote:
Hello, gurus
I have some problems with Oracle 10.2.0.3 on Windows 2003 32-bit.
We have PGA_AGGREGATE_TARGET set to 350 MB and a SGA of 2200 MB. Some of the
sessions are shared server ones (which take memory from the large pool), and
others are dedicated. Sometimes, when some big-fat report is running, the
actual PGA allocated grows up to 550 MB and more. Then we are getting
ora-4030, because we hit the 3 GB limit of 32 bit windows.
In this cases I can see that one dedicated connection (the one
running the big report) has allocated up to 280 MB PGA (this is, one
session!). We are not using parallel things, if it matters at all.
I know PGA_AGGREGATE_TARGET is just a target, not a limit. But I
wonder is there any way to limit how much PGA can a single session consume.
I thought there is a rule stating no session can eat more than 10% than the
total target, but this proved to be wrong.
--
Regards,
Yavor Ivanov
Senior Database Expert
Stemo Ltd
--
//www.freelists.org/webpage/oracle-l
Other related posts:
